Georgii Dolzhykov

Conceptually, Prettier doesn't preserve the existing formatting, it removes it. 🔥🔥🔥 There are a few exceptions to this (object literals, method decorators, and some cases in JSX), but those are...

> That’s what we had before. It didn’t work very well for simple expressions like Math.random().toString().split('.'). No, that's not the same thing as "if a chain contains a call with...

@rvion I strongly believe preserving manual formatting dilutes the value of Prettier. We all are used to the current semi-automatic formatting of object literals, but in fact it's a PITA....

@rvion > As a library author with dozen builder types libs with fluent apis, hundreds of files are now beeing reformated in a non consistent / weird and not readable...

@RikJansen81 > By doing so, I believe you're destroying a very important piece of information: intent How can we distinguish between a valuable intentional line break and a random line...

I really don't understand why it's a problem if ```js domain .concept('Page') .val('title') .vals() ``` gets reformatted into ```js domain.concept('Page').val('title').vals(); ``` I mean I see the problem in the original...

I would really like if anyone here who wants to say something in support of preserving existing new lines first reflected on https://github.com/prettier/prettier/issues/2068#issuecomment-307247952 and realized how such situations defeat the...

@rvion Prettier is well past that phase when a GitHub issue or a Twitter poll can be used to understand what the **majority** of users wants. As for #2068, preserving...

@rvion > there is a bug in prettier > because of this bug, some merging (= operation related to collaboration / unrelated to code quality) is made harder Not a...

@syabro @gms1 Your thoughts on #7889?