-
-
Notifications
You must be signed in to change notification settings - Fork 75
Imported types cause false positives with no-unused-vars
rule
#457
Comments
We cannot turn on Would really love to rely on eslint to check to allow compiling. |
I have this issue as well. Using the same workaround as kinyat via overrides (so I can still have these rules enabled in
|
There is already a custom rule in the plugin for If that rule is no sufficient for this use-case then a bug report should be filed against it, and ideally a PR submitted to extend at. Thanks! |
I was using that, it fails if you import types that don't have a value. 'no-unused-vars': 'error',
'typescript/no-unused-vars': 'error', // ERROR: 'Options' is defined but never used
import { VuetifyUseOptions as Options } from 'types'
...
// Even though I use it here as a type
export default function lang (config: Options['lang'] = {}): VuetifyLanguage { |
As per my previous message, a bug report should be filed against the plugin, this is not a parsing issue |
Forgot this was a separate repo 😅 Looks like there is already a few: |
What version of TypeScript are you using?
2.7.2
What version of
typescript-eslint-parser
are you using?14.0.0
What code were you trying to parse?
What did you expect to happen?
No errors are reported with the
no-unused-vars
rule onWhat happened?
The
no-unused-vars
rule was previously mentioned in the readme as having known issues. Now that it's removed I expected the above code to work.The text was updated successfully, but these errors were encountered: