-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Improve dotnet_analyzer_diagnostic.category Documentation #22248
Comments
I had some success looking at the titles for the various pages nested next to this one: https://docs.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/. Same for the neighboring style rules. For example, there's a page "Performance rules" which lists the rules in the "-performance" category. Not sure how that translates to the categories with multiple words in their names. I also found I could address all style rules with the "-style" category. But I agree that more explicit documentation would be helpful. |
Also tagging @gewarren and @mikadumont We ship CA code quality analyzers and IDE code style analyzers with .NET SDK, starting version 5.0 We should add both these pieces of documentation:
|
The documentation should also list which version of Visual Studio you need to use the new severity setting. |
well, are there updates here? I want to enable some categories, but I didn't know the name of them in the Editorconfig. |
Thanks for the ping. I'll try to make these updates this month (August). |
The official documentation does not mention
dotnet_analyzer_diagnostic.category-CodeQuality.severity
but it exists in Roslyn Analyzers here: https://github.com/dotnet/roslyn-analyzers/blob/master/.editorconfig#L185-L239.This documentation mentions that there are categories for rules and mentions 'Performance' but fails to list the categories.
Is there a list of categories we can see?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: