-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
feat: circular autofix/conflicting rules detection #19514
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
✅ Deploy Preview for docs-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
nzakas
left a comment
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.
The code looks good to me. Can we also add a troubleshooting page that describes this error and what to do about it? I can imagine someone seeing this error and not understanding what it means or what to do about it.
|
Added a troubleshooting page in e423966. |
nzakas
left a comment
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.
Just cleaned up the docs a bit, but otherwise LGTM.
Co-authored-by: Nicholas C. Zakas <[email protected]>
Co-authored-by: Nicholas C. Zakas <[email protected]>
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[x] Add something to the core
[ ] Other, please explain:
Fixes #17609.
What changes did you make? (Give an overview)
Updated
Linter#verifyAndFix()to check if the produced fix in a pass is the same as in the second previous pass, and in that case stop and emit a warning about conflicting rules.Is there anything you'd like reviewers to focus on?