4 ms·
Doesn't it defeat the idea of "one formatting to rule them all" if they change the rules?
by k__ 7y ago
Doesn't it defeat the idea of "one formatting to rule them all" if they change the rules?
- mirekrusin 7y agoThe king is dead, long live the king!
- gherkinnn 7y agoIt will be difficult to find adoption if you can’t make room for options like removing unnecessary semicolons.
- brlewis 7y agoI'm not sure how dedicated prettier is to "one formatting to rule them all" since it's configurable per-project. Switching between different projects with different prettier configuration is very low friction. Speaking for myself, I advocate "one formatting to rule them all" in terms of just taking defaults, and one of my arguments is that, if there's something universally wrong about a prettier default, then it should be changed universally. And if it isn't universally wrong, just go with the default.
- k__ 7y agoYes. Some things are obviously bugs, especially the chained line break problem. Bur the semicolons config they added back in the days just baffled me.
- tlrobinson 7y agoI don't think Prettier ever claimed to be the one true formatting everyone must use for it to be successful. It's a tool that formats code nicer then most other tools. Personally, I would rather a project use a formatting tool that outputs a format I don't like than not using a formatting tool at all. I just don't want to have to waste mental bandwidth on formatting ever again.
- k__ 7y agoReally? I had the impression Prettier follwed the spirit of Go fmt, which had that claim.
- capableweb 7y agoMaybe you're confusing StandardJS with Prettier?