-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Documentation for diagnostic codes used in repo #48151
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
Thanks for your PR, @divyeshio. Someone from the team will get assigned to your PR shortly and we'll get it reviewed. |
|
Good discoveries that this process reveals! My suspicion is the gaps in the diagnostic IDs are a result of user error (AKA creating a new analyzer and skipped a value) as opposed to intentional issues. |
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.
Thanks for your help, @divyeshio !
@captainsafia is there anything you're waiting for here ? If not, feel free to merge. |
Thanks @divyeshio .. looks like this is your 2nd PR here. We hope you will continue to contribute -- we have over 100 marked "help wanted". - let us know if you need help finding a particular type of issue to work on. |
Nope, this is good to merge! I'll in fact be making use of this in a current PR of mine. :) cc: @eerhardt |
Documentation for diagnostic codes used in repo
Description
We currently use diagnostic codes in several places in the repo:
Source generators
MVC analyzers
Framework analyzers
But don't have a central location that documents all of them.
Fixes #47287