You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, I have an .editorconfig file built up over quite some time. Every so often we go through the MS ones to see if there are any new relevant ones we want to change the severity of.
This brings up two points:
How do you deprecate/remove analyzers if MS implements a similar one? Probably better to not have conflicting behavior or double analyzers.
How do we know from the docs (without going through the changelog) when an analyzer was added? This is important when scanning through the docs to see new items.
An analyzer that duplicates functionality of built-in analyzer can be disabled by default. Sometimes the functionality is similar but not the same in which case the decision which analyzer should be disabled is left to the user.
If you would like to see the newly added analyzers in some other form then changelog, then improving the docs is definitely possible but could you describe more precisely how it should look like?
Product and Version Used:
VS 17.7.0
Roslynator 4.4.0
When reading through the analyzer docs (https://josefpihrt.github.io/docs/roslynator/analyzers) and determining which ones are relevant (and deciding on their severity), how do we know which of these analyzers are already present in the MS built in analyzers (https://github.com/dotnet/roslyn-analyzers/tree/main)?
For example, I have an .editorconfig file built up over quite some time. Every so often we go through the MS ones to see if there are any new relevant ones we want to change the severity of.
This brings up two points:
My .editorconfig file for reference: .editorconfig.txt
The text was updated successfully, but these errors were encountered: