Skip to content
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

Change category of Roslynator analyzers #866

Closed
josefpihrt opened this issue Dec 1, 2021 · 1 comment
Closed

Change category of Roslynator analyzers #866

josefpihrt opened this issue Dec 1, 2021 · 1 comment

Comments

@josefpihrt
Copy link
Collaborator

As a part of 4.0 release I would like to change category of all Roslynator analyzers.

Current state

Each analyzer has category such as Readability, Usage etc. I believe that these values have little to no benefit to users.

Proposed state

Change category for each analyzer in a following way:

  • Category Roslynator_Core for analyzers in package Roslynator.Analyzers
  • Category Roslynator_CodeAnalysis for analyzers in package Roslynator.CodeAnalysis.Analyzers
  • Category Roslynator_Formatting for analyzers in package Roslynator.Formatting.Analyzers

This change will make possible to enable/disable (or change the severity) for each analyzer with just 1-3 entries in EditorConfig:

dotnet_analyzer_diagnostic.category-Roslynator_Core.severity = <severity>
dotnet_analyzer_diagnostic.category-Roslynator_CodeAnalysis.severity = <severity>
dotnet_analyzer_diagnostic.category-Roslynator_Formatting.severity = <severity>

Drawbacks

Someone may be already using current categories values => it is a breaking change.

@tiesmaster
Copy link

This change will make possible to enable/disable (or change the severity) for each analyzer with just 1-3 entries in EditorConfig:

This would be awesome!! I'd definitely appreciate a change like that

@josefpihrt josefpihrt unpinned this issue Aug 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants