-
Notifications
You must be signed in to change notification settings - Fork 6k
Small fixes to configure rule severity section #20779
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
Conversation
`dotnet_diagnostic` and `dotnet_analyzer_diagnostic` prefixes are only used for configuring rule severities that are respected by the compiler. Non-severity editorconfig options are defined and respected by each analyzer package themselves, so we cannot control the key format for these options.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought the individual/category/all rule syntax was generic to more than just severity.
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we move the precedence section out from under severity if it applies more generally? E.g. does it apply to the code quality rules too?
Nope, that is specific to the severity precedence rules enforced by the compiler. Compiler cannot enforce generic option precedence settings, those are up to each analyzer package/assembly to enforce. |
dotnet_diagnostic
anddotnet_analyzer_diagnostic
prefixes are only used for configuring rule severities that are respected by the compiler. Non-severity editorconfig options are defined and respected by each analyzer package themselves, so we cannot control the key format for these options.