Prettier 2.0 – Opinionated JavaScript formatter
1–10 of 91 posts
Re: Prettier 2.0 – Opinionated JavaScript formatter
#2Re: Prettier 2.0 – Opinionated JavaScript formatter
#3Did they change an option to disable lineWidth? In 1.* it was not possible, which was my single biggest issue with Prettier.
Many times it made code less coherent, due to forcing a few lines to be collapsed into one.
See Prettier example in ESLint section of "How I Learned to Stop Worrying and Love the Types & Tests", https://p.migdal.pl/2020/03/02/types-tests-typescript.html#e....
Re: Prettier 2.0 – Opinionated JavaScript formatter
#4finally you can run `npx prettier --write .` and get a folder formatted without any installation or configuration. This is a great decision. Congratulations on the release team!
Re: Prettier 2.0 – Opinionated JavaScript formatter
#5Did they change an option to disable lineWidth? In 1.* it was not possible, which was my single biggest issue with Prettier. Many times it made code less coherent, due to forcing a few lines to be collapsed into one. See Prettier example in ESLint section of "How I Learned to Stop Worrying and Love the Types & Tests", https://p.migdal.pl/2020/03/02/types-tests-typescript.html#e... .
Why not just change it to a high value? Or prettier-ignore exceptional lines?
Re: Prettier 2.0 – Opinionated JavaScript formatter
#6Prettier is one of my favourite pieces of software! I only wish they had a binary that doesn’t rely on Node.js
Re: Prettier 2.0 – Opinionated JavaScript formatter
#7finally you can run `npx prettier --write .` and get a folder formatted without any installation or configuration. This is a great decision. Congratulations on the release team!
That's probably useful in some cases but I'd still recommend pinning the version, since different versions of prettier format code differently and different team members will end up with conflicting changes.
Re: Prettier 2.0 – Opinionated JavaScript formatter
#8Did they change an option to disable lineWidth? In 1.* it was not possible, which was my single biggest issue with Prettier. Many times it made code less coherent, due to forcing a few lines to be collapsed into one. See Prettier example in ESLint section of "How I Learned to Stop Worrying and Love the Types & Tests", https://p.migdal.pl/2020/03/02/types-tests-typescript.html#e... .
This isn’t really possible due to Prettier’s design, unfortunately. It basically lays out each statement on one line until it gets to the maximum width, then tries a variety of ways to break the line until it’s under the limit.
We also don’t want to look at how the code is formatted coming in because one of Prettier’s goals is to make sure everyone’s code looks the same, which wouldn’t be possible if we looked at how the input is formatted too much.
Re: Prettier 2.0 – Opinionated JavaScript formatter
#9Did they change an option to disable lineWidth? In 1.* it was not possible, which was my single biggest issue with Prettier. Many times it made code less coherent, due to forcing a few lines to be collapsed into one. See Prettier example in ESLint section of "How I Learned to Stop Worrying and Love the Types & Tests", https://p.migdal.pl/2020/03/02/types-tests-typescript.html#e... .
Why not just change it to a high value? Or prettier-ignore exceptional lines?
Then it wraps longer statements into one line. Which for things of unrestricted length (e.g. arrays) is not an option.
Re: Prettier 2.0 – Opinionated JavaScript formatter
#10Did they change an option to disable lineWidth? In 1.* it was not possible, which was my single biggest issue with Prettier. Many times it made code less coherent, due to forcing a few lines to be collapsed into one. See Prettier example in ESLint section of "How I Learned to Stop Worrying and Love the Types & Tests", https://p.migdal.pl/2020/03/02/types-tests-typescript.html#e... .
Why not just change it to a high value? Or prettier-ignore exceptional lines?
if you put a high lineWidth value, you'll have your object literals or destructuring mostly one-lined, etc.. often not desirable (for 4+ props)
That's mostly why I don't like prettier, sometimes you want a bit of control over code formatting when several options are possible, prettier don't allow it. I use vscode formatter (actually it's TypeScript compiler formatter) instead
Other things I dislike with prettier, like how it'd force parenthesis in a `2 + 3 * 4` expression, where it's a bit superfluous. Or string templates line returns on expressions https://github.com/prettier/prettier/issues/3280