[no-unused-vars] false positive when generic param name masks name in parent scope about typescript-eslint HOT 2 CLOSED

Digging into this, I don't know what we can do about this without significant work.

Right now our rule sits on top of the base rule, so I think we would have to clone the base rule's code in order to handle this case properly.

This would be a good candidate for using the TS parser services if it reports unused vars.

This should be caught by something like no-redeclare. Though it won't because we haven't added ts-specific handling to that rule.

from typescript-eslint.

@bradzacher right now there is no real solution for that. It's require some work on parser before we can start.
I started doing PR with support for additional data in scope for typescript "types" but its not near finish.
When it will be done, we can start thinking about solving this.

I made this issue for now just to inform ppl that we are aware about it and we will work on it.

no-redeclare is not possible now without scope analysis (unless we do it in bad way on our side)

type references and annotations are not in eslint scope for now.

from typescript-eslint.