-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EditorConfig user interface #39414
Labels
Area-IDE
Feature Request
Need Design Review
The end user experience design needs to be reviewed and approved.
Milestone
Comments
jinujoseph
added
Area-IDE
Feature Request
Need Design Review
The end user experience design needs to be reviewed and approved.
labels
Oct 21, 2019
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area-IDE
Feature Request
Need Design Review
The end user experience design needs to be reviewed and approved.
Goal:
Create a user interface to eliminate tension when configuring analyzer rules. This should also work for third-party analyzer packages.
Current Behavior:
Can configure the severity level of an analyzer through an EditorConfig file:
Can configure the severity level of an analyzer through the editor and error list:
Can configure the severity level of an analyzer through Tools Options:
Issues with current options:
It is difficult to configure naming conventions.
It is difficult to remember and understand the EditorConfig syntax.
The current tools options UI is only for code style / IDE analyzers and should have one UI for every type of analyzer.
The current tools options UI is hard to use without a search bar.
The current tools options UI has to be manually updated each time a new analyzer is created.
Expected Behavior:
Have a dynamic EditorConfig settings UI similar to VS Code’s Settings UI:
The EditorConfig settings UI should work for third party analyzers:
VS Code already supports this with extensions in their settings UI page by using contribution points.
The text was updated successfully, but these errors were encountered: