Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
Closed
Description
Before You File a Bug Report Please Confirm You Have Done The Following...
- I have tried restarting my IDE and the issue persists.
- I have updated to the latest version of the packages.
- I havesearched for related issues and found none that matched my issue.
- I haveread the FAQ and my problem is not listed.
Playground Link
Repro Code
The minimal reproduction is as follows:
declareclassSomeClass{someMethod(methodParam:any);// ❌ `'methodParam' is already declared in the upper scope`}functionmethodParam(){}
If, however,function methodParam is instead avar,let orconst declaration, the ESLint error is not triggered.
Quite a few more examples of this strange behavior are in the playground link.
ESLint Config
module.exports={parser:"@typescript-eslint/parser",rules:{"@typescript-eslint/no-shadow":"error"},};
tsconfig
{"compilerOptions": {"strictNullChecks":true }}Expected Result
The error should always be reported or not reported no matter with what type of declaration the name of the parameter inside an ambient declaration clashes.
I personally can't tell whether it's technically shadowing or not. Perhaps having an option to treat clashes between real and ambient declarations' names as shadowing issues could be the solution.
Actual Result
The current behavior seems inconsistent to me.
Additional Info
No response