Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
Description
I'm exploring if it's possible to write a rule that warns against// @ts-ignore
comments that have become stale as result of changes in other places of even on the line that tsc is being ignored. My approach is to get all diagnostics and cross reference them with// @ts-ignore
comments and see which comment does not actually ignoring an error. But if the// @ts-ignore
comment is still there TypeScript will not report any diagnostics for the next line.
Is there any way of getting diagnosticsif we remove the// @ts-ignore
comment?
One solution is to remove all// @ts-ignore
comments from source files of existing program, construct a new program with those source files and get diagnostics. This seems very very expensive
Any thoughts on this?
Versions
package | version |
---|---|
@typescript-eslint/eslint-plugin | 1.3.0 |
TypeScript | 3.0 |