-
Notifications
You must be signed in to change notification settings - Fork 889
Relax 'recommended' rules or make them auto-fixable #4305
Comments
Strong +1 to this. It's been brought up before. Anything that's enabled in |
Taking another look at this - technically, this would be a breaking change. Still accepting PRs but they'll likely have to wait until 6.0.0 to be merged in. |
Agreed that this is a breaking change and I agree that formatters should do formatting, not linters. I recently started a new typescript project, took
Can we get a proposal for what the new set would be? We could put in a new preset for |
@ericanderson Me too, but there are fixable rules. Alphabetically sorting your keys is cool, but adding it to existing projects is suffering. A fixer would be really really nice, but I guess that would also go in a separate issue. Any links you can gimme? |
Removing the |
🤖 Beep boop! 👉 TSLint is deprecated 👈 and you should switch to typescript-eslint! 🤖 🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋 |
The recommended rules include some (imho) impossible rules to abide by. Sorting your object keys? Why would I want them alphabetic if they made more sense in some other ordering? Furthermore, it's not a fixable rule, it just complains. I am a huge fan of Typescript and consider linting a very important tool. However, rules like:
are too opinionated and prove a burden on the programmer who already has lots of problems to solve while developing a project. The set of 'recommended' rules should, in my opinion, be much more lax than that to reduce the barrier of entry to Typescript and tslint. They should be guiding and helpful, not opinionated and pedantic.
I propose removing the more 'extreme' rules from the recommended ruleset.
The text was updated successfully, but these errors were encountered: