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

Contrast with MS analyzers and updated dates #1159

Open
dylanvdmerwe opened this issue Aug 15, 2023 · 1 comment
Open

Contrast with MS analyzers and updated dates #1159

dylanvdmerwe opened this issue Aug 15, 2023 · 1 comment

Comments

@dylanvdmerwe
Copy link

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:

  1. How do you deprecate/remove analyzers if MS implements a similar one? Probably better to not have conflicting behavior or double analyzers.
  2. 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.

My .editorconfig file for reference: .editorconfig.txt

@josefpihrt
Copy link
Collaborator

Hi,

  1. 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.

  2. 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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants