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.
Wow, tslint has improved so much - awesome! However, there are so many new rules now it's hard to keep track of them.
Is there a way to list all rules that haven't been explicitly specified in your tslint.json?
That way, when new rules come out, I can just run a command, look at the list of new rules that aren't specified in my tslint.json, read up on the documentation and specify them. This is better than my suboptimal eyeballing at the moment.
The text was updated successfully, but these errors were encountered:
Fair point. We're working on a tslint:all configuration that lists all the rules (#2417). Do you think that sufficiently addresses this problem?
It would also be pretty easy to write a Node script to compare your list of configured rules to the list of files that match node_modules/tslint/lib/rules/*Rule.js. This code does something close to this.
How about if you use custom rules, like tslint-react, etc.?
Is there some code path which reads the extends & rulesDirectory settings and makes a list of every single rule available? Then I can use this to diff against tslint.json.
Thanks for that check-tslint-all! This seems out of scope for TSLint itself, so closing this issue for now. If there's a spike in interest we can always revisit.
Wow, tslint has improved so much - awesome! However, there are so many new rules now it's hard to keep track of them.
Is there a way to list all rules that haven't been explicitly specified in your tslint.json?
That way, when new rules come out, I can just run a command, look at the list of new rules that aren't specified in my
tslint.json
, read up on the documentation and specify them. This is better than my suboptimal eyeballing at the moment.The text was updated successfully, but these errors were encountered: