Lily Skye

> Maybe a better rule would be "always break nested object patterns onto multiple lines", rather than looking at the source. Though that rule might have to only apply to...

@Slapbox you can use the online prettier playground here: https://prettier.io/playground/ The "Copy markdown" button in the bottom right is very useful when sharing results on GitHub.

It's pretty complicated, but it seems like a good heuristic. However, I think that: * N, M, and O should *NOT* be configurable * This should only apply to object...

Actually, thinking about it some more, I think N, M, and O should be based more on print width and less on arbitrary numbers, otherwise we will introduce confusing style...

How about: An object is "simple" if it only contains shorthand properties, and is "complex" otherwise. An array is "simple" if it contains no computed properties. Rules: If an object...

I'm a bit confused; all your examples are object and array literals, not destructuring patterns. I thought this issue was about destructuring patterns

Hi @jdheeter, could you open a new issue around your specific case using the prettier playground to demonstrate? There are instructions for using the playground in the issue template.

This feature would be nice to have, mostly for monorepos, but also for deeply nested build output directories. My first intuition was that this would be supported (because I was...

Yes

I'm open to that :+1: