-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[no-unsafe-member-access] Namespaces trigger error #1868
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
Could you please create a repro repo for this? I suspect that there is an issue with your config. |
@bradzacher Please see: https://github.com/mf-pherlihy/typescript-eslint-no-unsafe-member-access
|
interesting. It looks like it's an error due to v I'm not sure what is happening. |
doing a pseudo-bisect shows that this is broken from v |
I have a repro without any of our packages, so I'm not sure what the problem is. I'll need to keep looking |
Looks like you stumbled upon a bug in typescript! |
I can still reproduce this with
the linked issue is supposedly fixed since typescript 4.0.1 namespace A {
export interface B {}
}
export interface C extends A.B {} // Unsafe member access .B on an any value. eslint(@typescript-eslint/no-unsafe-member-access) |
that bug is unrelated to this bug - please file a new issue. This bug is fixed in TS 4.0.1+ |
Repro
Expected Result
No error
Actual Result
Additional Info
Pretty simple to reproduce, just create a definition file and have a class that extends the
NodeJS.EventEmitter
class.Versions
@typescript-eslint/eslint-plugin
2.27.0
@typescript-eslint/parser
2.27.0
TypeScript
3.8.3
ESLint
6.8.0
node
10.18.1
npm
6.13.4
The text was updated successfully, but these errors were encountered: