Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
Open
Description
Before You File a Proposal Please Confirm You Have Done The Following...
- I havesearched for related issues and found none that match my proposal.
- I have searched thecurrent rule list and found no rules that match my proposal.
- I haveread the FAQ and my problem is not listed.
My proposal is suitable for this project
- I believe my proposal would be useful to the broader TypeScript community (meaning it is not a niche proposal).
Link to the rule's documentation
https://typescript-eslint.io/rules/no-mixed-enums
Description
I'd added this TODO a year ago but never filed an issue for it:
typescript-eslint/packages/eslint-plugin/src/rules/no-mixed-enums.ts
Lines 164 to 170 in2373a63
| // TODO: We don't need to dip into the TypeScript type checker here! | |
| // Merged namespaces must all exist in the same file. | |
| // We could instead compare this file's nodes to find the merges. | |
| consttsNode=parserServices.esTreeNodeToTSNodeMap.get(node.id); | |
| constdeclarations=typeChecker | |
| .getSymbolAtLocation(tsNode)! | |
| .getDeclarations()!; |
Additional Info
Marking asrefactor rather thanenhancement orperformance as it likely won't noticeably improve rule performance in 99.9% of cases.