Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
fix(eslint): add prettier rules if installed without TS #74
Conversation
Currently, it will only add the prettier rules if Typescript is also installed
|
why this is not merged yet? |
|
The problem is, not everyone needs this thing (even for TypeScript, so we need a way to disable this behavior). |
|
this can be as a question in |
|
Also I would suggest to add https://github.com/prettier/eslint-plugin-prettier |
Yep.
I believe you can already define it in your config but we won't have it by default (or even with an option) because of the very bed developer experience it creates. We shouldn't treat unformatted code as an error and distract developers but format it silently on commit. |
|
All major IDE has built-in ability fix eslint issues on save and this is not bad expanse for fast developing |
The problem
Currently, the task will only add the prettier rules if Typescript is also
installed.
What was changed
eslint-config-prettierif prettier is installed, regardless of TS