prettier/tests/object_colon_bug/__snapshots__/jsfmt.spec.js.snap

// Jest Snapshot v1, https://goo.gl/fbAQLP

exports[`bug.js 1`] = `
"const foo = {
  bar: props.bar ? props.bar : noop,
  baz: props.baz
}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
const foo = {
  bar: props.bar
    ? props.bar
    : noop,
  baz: props.baz
};
"
`;
Upgrade to Jest 19 (#762) * Upgrade to Jest 19 * Use exact versions for Jest 2017-02-22 00:59:19 +03:00			`// Jest Snapshot v1, https://goo.gl/fbAQLP`

Revert "Improve snapshot naming" (#1070) * Revert "Remove mutation in `printBinaryishExpressions` (#1067)" This reverts commit e7312ad7b2469fc402af705e661e8a026b66749b. * Revert "Make it clear what parser was used in each snapshot (#1068)" This reverts commit 4f7ae4815b67c4da9ec339e49ce57602195e7bf7. 2017-03-22 03:38:28 +03:00			exports[`bug.js 1`] = `
Remove extra group when printing object values (#502) It turns out that in an unlikely turn of event, the inner group can be inline and not print the opening paren but the outer group breaks and outputs the closing paren which generates invalid JavaScript. I tried removing the group altogether and no tests failed, so I'm assuming the group wasn't needed in the first place. If it was, we should add tests to cover this. Fixes #501 2017-01-30 18:03:40 +03:00			`"const foo = {`
			`bar: props.bar ? props.bar : noop,`
			`baz: props.baz`
			`}`
			`~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
			`const foo = {`
[RFC] Remove parenthesis object special case (#689) I've started the discussion around it but I think that it was a mistake. It feels weird to add parenthesis on object values sometimes but not others. I think that it's best to let prettier do its work on staying under 80 columns based on the rules we added. 2017-02-15 18:20:37 +03:00			`bar: props.bar`
			`? props.bar`
			`: noop,`
Remove extra group when printing object values (#502) It turns out that in an unlikely turn of event, the inner group can be inline and not print the opening paren but the outer group breaks and outputs the closing paren which generates invalid JavaScript. I tried removing the group altogether and no tests failed, so I'm assuming the group wasn't needed in the first place. If it was, we should add tests to cover this. Fixes #501 2017-01-30 18:03:40 +03:00			`baz: props.baz`
			`};`
			`"`
			`;