Hacker News new | past | comments | ask | show | jobs | submit login

Prettier often makes code written using sequences of .chaining much more difficult to read by forcing it all to the same line.

For the same reason, it often makes code written using composition more difficult to read since it won't let you decide when to put a sub-call on its own indented line for clarity.




I had the same gripe, and recently tried switching to dprint. It is much less aggressive with changing where lines break, and honestly it’s a huge relief to be able to break lines wherever I think makes the code most readable. It’s also significantly faster than prettier. I’ve been very happy with it.


dprint is soo much better (configurable) and already written in Rust so very fast

I am sad it's not getting more popular


In those situations I make use of comments to force new lines where I want them. Stupid but it works!


Disable it! (https://prettier.io/docs/en/ignore.html)

I do this occasionally, and especially with things like test tables. Linters/formatters are there to help in the common case, not to be some oppressive dogma.


If the fix is to disable prettier for an entire file, you're proving your parent poster point.


It doesn't have to be disabled for the whole file, you can annotate lines too as shown in the link the parent commenter shared.


Adding comments just to fight with prettier is... uglier. I rather just not use prettier at all. It's more harmful than good IMO.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: