Tslint rules are barriers to entry #450
Description
Ever since I started using create-react-app for my Typescript projects, I've noticed that I have to disable quite a few impossible linting rules that make life very hard for a newcomer to this project.
Rules like:
- interface-name
- member-access
- object-literal-sort-keys (wtf?)
- ordered-imports (again, wtf?)
These are rules that are too opinionated in my humble opinion. Furthermore, they are not automatically fixable. Instead, the whole project refuses to compile and shows an overlay on top of the web page. I suggest not using all the 'recommended' rules from the start.
As a hacker who uses your project to quickstart an application, I find that it makes life harder, not easier, in this aspect.
What's even more annoying is that even if you disable the rule you don't like, you have to restart the bundler to see the change in effect.
I understand that these are the official recommended rules from tslint (curated by some kind of pedantic sadomasochist), but there must be a middle ground that we can reach, especially if the user is new to Typescript, to encourage newcomers to use Typescript in their React apps instead of finding it too hard and ditching it altogether.