Jed Fox

Why don’t you want Prettier to format the HTML inside the template strings? Does it break your code’s syntax?

Perhaps we should keep single-line HTML literals single-line? How about renaming your template tag `expect`? That would fit in with its usage, and it avoids the formatting issue.

@jakepark #1733 has been reverted.

I like how the code in #4184 is formatted. If the JSX goes past the print width, it’ll be broken onto multiple lines and wrapped with parens. Have you set...

> Prettier opines on the existing formatting, which often times are human-formatted for readability. Massive, unnecessary diffs may result. This is an unfortunate side effect of an opinionated code formatter’s...

@jakepark The difference is that JSX ignores whitespace that includes newlines, whereas HTML doesn’t.

> In other words, Prettier can't do anything based on the way you had formatted something, because it is designed to throw out everything you had before and just generate...

@Favna why can’t you disable the ESLint rule?

@finalclass I can’t reproduce that on the playground: **Prettier 1.12.1** [Playground link](https://prettier.io/playground/#N4Igxg9gdgLgprEAuc0DOMAExMENMC+mAvNgQNwA6UIANCBAA4wCW6youATlxAO4AFbgjTIQuAG4QWAEzogARl1xgA1nBgBlRipZQA5shhcArnHp60cLjAHL9AW1zIAZrgA2V+gCs0ADwAhZTUNTVwHOAAZPThXDy8QHS4rLjEFXAUAT3doeUYuPRgAdVkYAAtkAA4ABnp8iCsi5UYxfLgUiVj6LjgARxMWHrtcR2ckN09zECsHFiNTKbQ9fXc4AEUTCHg4yfoYDJKZcuQAJj3lFndlgGEIBycxKGgukBMrABUM0XH4uAICIA) **Input:** ```jsx const { a } = {}; ``` **Output:** ```jsx const { a } = {}; ```...

Now that it’s less of a hassle to collapse expanded objects, perhaps this would be OK to do.