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
no-unused-vars errors with parameters when parameter marked used later #10952
Comments
Hi @webOS101, thanks for the issue. Would you mind running ESLint with the |
It's not that, sadly. I had checked that previously.
|
It may be as simple as checking eslint/lib/rules/no-unused-vars.js Line 472 in 648a33a
But I didn't actually test that. |
I confirmed that works. I was able to create a test case that fails and passes with that fix. I still have never figured out how to use a locally linked eslint to test with either global or local installs. I guess I'll figure it out someday. I'll create a PR shortly. |
Thanks @webOS101 for digging further! I think I rewrote that code some time ago and this was an oversight on my part. I've relabeled this as a bug, in accordance with your investigation results. |
Tell us about your environment
What parser (default, Babel-ESLint, etc.) are you using? babel-eslint
Please show your full configuration:
Configuration
What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.
The eslint-plugin-react rule for
jsx-uses-vars
marks theWrapped
parameter as used. However,no-unused-vars
doesn't update the status ofconfig
. The default forno-unused-vars
should not warn on parameters before the first used parameter.eslint .
What did you expect to happen?
No warnings.
What actually happened? Please include the actual, raw output from ESLint.
Linked issue: jsx-eslint/eslint-plugin-react#2009
The text was updated successfully, but these errors were encountered: