-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
docs: explain no-unused-vars advantages over TypeScript #7347
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
docs: explain no-unused-vars advantages over TypeScript #7347
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. |
@@ -6,7 +6,22 @@ description: 'Disallow unused variables.' | |||
> | |||
> See **https://typescript-eslint.io/rules/no-unused-vars** for documentation. | |||
|
|||
## Examples |
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.
PR Checklist
@typescript-eslint/no-unused-vars
different than TypeScript’s own errors? #4641Overview
Adds a summary of the information in the issue.
Honestly, this is 3/4 along the way to being its own blog post. I'll probably eventually write one about the blurry lines between linting and type checking...