Fix: prefer-const
false negative about eslintUsed
(fixes #5837)
#6971
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.
Fixes #5837.
This PR makes
prefer-const
warning used variables bycontext.markVariableAsUsed(name)
API, on except global scope./*exported*/
comments also are usingeslintUsed
.I thought
prefer-const
should not warnfoo
in the following code.prefer-const
still ignore used global variables bycontext.markVariableAsUsed(name)
API (since/*exported*/
comment is applied to only global variables).But this PR will improve the issue.
In most cases, the variables that
react/jsx-use-vars
marks are on Node.js/CommonJS scope or Module scope.EDIT: This needs minor bump since this will increase warnings.