ESLint Config Migration: Allow unused vars with leading underscores #1045
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
26 tasks
seratch
approved these changes
Aug 10, 2021
| '@typescript-eslint/no-unused-vars': [ | ||
| 'error', | ||
| { | ||
| varsIgnorePattern: '^_', |
misscoded
approved these changes
Aug 13, 2021
stevengill
approved these changes
Aug 18, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This is a PR that should be merged into #1024 and incrementally addresses #842.
This PR turns extends the
@typescript-eslint/no-unused-vars rule(for reference: base ESLintno-unused-varsrule).Leading underscores are allowed for variable and argument names and is intended to signify "ignore this variable."
Impact
Before
After
Requirements (place an
xin each[ ])