-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
test(eslint-plugin): add docs test for Correct and Incorrect blocks #9239
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
test(eslint-plugin): add docs test for Correct and Incorrect blocks #9239
Conversation
Thanks for the PR, @JoshuaKGoldberg! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There are probably some complex situations (for example, https://typescript-eslint.io/rules/ban-ts-comment/ is actually fine), but we can fix the invalid ones first |
PR Checklist
Overview
Following #8015, this adds additional testing to ensure there's both a ✅ Correct and an ❌ Incorrect tab item for each rule option.
A lot of existing rule docs don't yet adhere to this. Rather than try to fix them all in this PR, I added an allowlist with a TODO comment.
💖