-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[no-unused-vars] warning for used vars #171
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
Comments
We have the same issue. Workaround is to lock |
regression got fixed in @1.1.2-alpha.5, 6147de1 |
As this has been fixed, I'll close this issue. |
Still receiving this error as of |
@gabemeola can you provide some example (source code)? |
@gabemeola there are a number of false positive cases for no-unused-vars. Please open a new issue with a code sample, so we can investigate appropriately. |
Repro
I get many alerts from eslint because I have supposedly unused variables. For Example in this File.
Expected Result
no eslint warnings, scince all variables are used at some point.
Actual Result
4:8 warning 'style' is defined but never used @typescript-eslint/no-unused-vars
17:5 warning 'saveTodo' is defined but never used @typescript-eslint/no-unused-vars
18:5 warning 'removeTodo' is defined but never used @typescript-eslint/no-unused-vars
19:5 warning 'isLoading' is defined but never used @typescript-eslint/no-unused-vars
30:11 warning 'addNewTodo' is assigned a value but never used @typescript-eslint/no-unused-vars
35:36 warning 'todo' is defined but never used @typescript-eslint/no-unused-vars
Additional Info
I just migrated from https://www.npmjs.com/package/eslint-plugin-typescript. While using that package, there was no warnings.
Versions
@typescript-eslint/eslint-plugin
1.1.1
@typescript-eslint/parser
1.1.1
TypeScript
3.2.4
ESLint
5.12.1
node
10.14.1
npm
6.5.0
The text was updated successfully, but these errors were encountered: