You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
Is your feature request related to a problem? Please describe.
Anecdotally there are likely many places in a lot of code bases where // tslint:disable-next-lineused to be used on a place but no longer is. It's nice to be clean, and a little more nice to not be misleading. I've seen people copy & paste these comments and not know what they're for within the linter.
Describe the solution you'd like
Flow has a nifty feature with $FlowFixMe where it complains if you use it unnecessarily. Can we add a flag to TSLint to enable this kind of post-lint check?
Describe alternatives you've considered
We can't make this into a rule because the individual rules don't have access to this kind of accumulated info (right?).
The text was updated successfully, but these errors were encountered:
ESLint has this option. Obviously it's a different tool with different infrastructure, but we might be able to get some inspiration from how it's implemented.
This option causes ESLint to report directive comments like // eslint-disable-line when no errors would have been reported on that line anyway. This can be useful to prevent future errors from unexpectedly being suppressed, by cleaning up old eslint-disable comments which are no longer applicable.
Feature request
Is your feature request related to a problem? Please describe.
Anecdotally there are likely many places in a lot of code bases where
// tslint:disable-next-line
used to be used on a place but no longer is. It's nice to be clean, and a little more nice to not be misleading. I've seen people copy & paste these comments and not know what they're for within the linter.Describe the solution you'd like
Flow has a nifty feature with
$FlowFixMe
where it complains if you use it unnecessarily. Can we add a flag to TSLint to enable this kind of post-lint check?Describe alternatives you've considered
We can't make this into a rule because the individual rules don't have access to this kind of accumulated info (right?).
The text was updated successfully, but these errors were encountered: