You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
leta=[{a: 'a longer string',b: 'an even longer string'}];leta=[{a: 'a longer string',b: 'an even longer string'}];leta=[{a: 'a longer string',b: 'an even longer string'}];leta=[{a: 'a longer string',b: 'an even longer string'}];
Output:
leta=[{a: 'a longer string',b: 'an even longer string'}];leta=[{a: 'a longer string',b: 'an even longer string'}];leta=[{a: 'a longer string',b: 'an even longer string'}];leta=[{a: 'a longer string',b: 'an even longer string'}];
Expected behavior:
I would expect Prettier's opinion on how this object to look to be consistent regardless of how the user initially typed it. At the moment, there are (at least) two possible answers for how Prettier will format the same code.
The text was updated successfully, but these errors were encountered:
👋 @EricG-Personal! Please see #2068 and #11856. This behaviour has been a long-standing trade-off between the deterministic behaviour and output ugliness. Thoughts are welcome in #2068!
Prettier 2.6.1
Playground link
Input:
Output:
Expected behavior:
I would expect Prettier's opinion on how this object to look to be consistent regardless of how the user initially typed it. At the moment, there are (at least) two possible answers for how Prettier will format the same code.
The text was updated successfully, but these errors were encountered: