vitalif
/
prettier
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
prettier/tests/line_suffix_boundary/__snapshots__/jsfmt.spec.js.snap

104 lines
1.7 KiB
Plaintext
Raw Normal View History

Introduce line-suffix-boundary (#750) The idea is that if you reach the end of the `}` inside of a template literal, we have to flush the trailing comma, otherwise it would generate invalid code. We also need the same special case for JSX. I don't like adding yet another type of document but it seems like the most elegant way to solve the problem. Fixes #623
2017-02-23 20:26:26 +03:00
// Jest Snapshot v1, https://goo.gl/fbAQLP
Make it clear what parser was used in each snapshot (#1068)
2017-03-22 00:47:23 +03:00
exports[`boundary.js-babylon 1`] = `
Introduce line-suffix-boundary (#750) The idea is that if you reach the end of the `}` inside of a template literal, we have to flush the trailing comma, otherwise it would generate invalid code. We also need the same special case for JSX. I don't like adding yet another type of document but it seems like the most elegant way to solve the problem. Fixes #623
2017-02-23 20:26:26 +03:00
"\`\${
a + // a
a
}
\${a // comment
}
\${b /* comment */}
\${/* comment */ c /* comment */}
\${// comment
d //comment
}
\${// $FlowFixMe found when converting React.createClass to ES6
ExampleStory.getFragment('story')}
\`;
<div>
{ExampleStory.getFragment('story') // $FlowFixMe found when converting React.createClass to ES6
}
</div>;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
\`\${a + a // a
}
\${/* comment*/
a}
\${/* comment */ b}
\${/* comment */ /* comment */ c}
\${/* comment*/
/*comment*/
d}
\${/* $FlowFixMe found when converting React.createClass to ES6*/
ExampleStory.getFragment(\\"story\\")}
\`;
<div>
{ExampleStory.getFragment(\\"story\\") // $FlowFixMe found when converting React.createClass to ES6
}
</div>;
"
`;
Make it clear what parser was used in each snapshot (#1068)
2017-03-22 00:47:23 +03:00
exports[`boundary.js-flow 1`] = `
Introduce line-suffix-boundary (#750) The idea is that if you reach the end of the `}` inside of a template literal, we have to flush the trailing comma, otherwise it would generate invalid code. We also need the same special case for JSX. I don't like adding yet another type of document but it seems like the most elegant way to solve the problem. Fixes #623
2017-02-23 20:26:26 +03:00
"\`\${
a + // a
a
}
\${a // comment
}
\${b /* comment */}
\${/* comment */ c /* comment */}
\${// comment
d //comment
}
\${// $FlowFixMe found when converting React.createClass to ES6
ExampleStory.getFragment('story')}
\`;
<div>
{ExampleStory.getFragment('story') // $FlowFixMe found when converting React.createClass to ES6
}
</div>;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
\`\${a + a // a
}
\${/* comment*/
a}
\${/* comment */ b}
\${/* comment */ /* comment */ c}
\${/* comment*/
/*comment*/
d}
\${/* $FlowFixMe found when converting React.createClass to ES6*/
ExampleStory.getFragment(\\"story\\")}
\`;
<div>
{ExampleStory.getFragment(\\"story\\") // $FlowFixMe found when converting React.createClass to ES6
}
</div>;
"
`;