-
-
Notifications
You must be signed in to change notification settings - Fork 485
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
Revamp analyzer diagnostic system #4626
Comments
Are there some rationales for using |
There are no particular rationales, feel free to propose something in here. |
Maybe we should use the default implementation of Severity that should be |
That's a variant that doesn't exist in |
Indeed, I had some understanding. Looks good to me. |
Our analyzer currently works this way:
This behaviour is different from the majority of linters/analyzers out there, and it's really confusing for people who use other tools. We intended to change it, so:
Severity::Information
by default)This means there could be lint rules that will have
Severity::Warning
rules and be recommended.The text was updated successfully, but these errors were encountered: