85e0bffa7d
Removed injectGlobal and keyframes ( #2342 )
2017-06-28 16:03:33 -07:00
968cc3cb2b
Delete fuzzer2.js
2017-06-29 08:52:14 +10:00
067a0137bd
Add support for css, keyframes and injectGlobal keywords ( #2337 )
...
* styled components now support css keyword
* added support also for keyframes
* added comment to reflect the new keywords
* modified comment
* ignore css and keyframes when testing ast manipulations
* added also injectGlobal
2017-06-28 14:31:27 -07:00
20a0723fc1
Convert build.sh into build.js using shelljs
...
For better cross platform compatibility.
2017-06-28 22:34:59 +02:00
ba51d2dfa8
Enable linting of build scripts
2017-06-28 21:37:33 +02:00
21733e441d
Normalize ALE headers in Vim docs
2017-06-28 12:37:37 -04:00
175cde1dc5
Force trailingComma option to "none" when parser is JSON ( #2335 )
...
* Run JSON tests with `trailingComma: "all"`
* Add test of `parser: 'json', trailingComma: 'all'` with non-.json extension
See https://github.com/prettier/prettier/issues/2308#issuecomment-311707801
* Force trailingComma option to "none" when parser is JSON
This fixes https://github.com/prettier/prettier/issues/2308
2017-06-28 09:29:47 -07:00
8e37fd76e9
Add support for range-formatting GraphQL ( #2319 )
...
* Add test for range-formatting GraphQL
See https://github.com/prettier/prettier/issues/2296#issue-238985580
* Pass test for range-formatting GraphQL
See https://facebook.github.io/graphql/#sec-Appendix-Grammar-Summary.Query-Document
This fixes https://github.com/prettier/prettier/issues/2296
* Consider *Definition GraphQL nodes to be formattable
See https://github.com/prettier/prettier/pull/2319#discussion_r124569400
2017-06-28 09:21:11 -07:00
9ee3e581d4
(docs): Document using Prettier + Vim using ALE ( #2333 )
2017-06-28 09:20:34 -07:00
678964b8de
fix(typescript): don't add namespace keyword to global declaration, fixes #2327 ( #2329 )
2017-06-28 07:53:10 -07:00
5db9407d78
1.5.2
2017-06-27 20:33:35 -07:00
b231948a36
GraphQL: Print directives for field declarations ( #2317 )
2017-06-27 20:22:03 -07:00
45c8e40d8a
GraphQL: Implement schema ( #2316 )
2017-06-27 20:15:55 -07:00
019beb54e5
GraphQL: Fix directives separator ( #2315 )
...
I couldn't figure out what the separator was, I tried `,`, `on` but none of them worked. Turns out it is `|`!
2017-06-27 19:58:38 -07:00
14caabd635
GraphQL: Print arguments for FieldDefinition ( #2314 )
2017-06-27 19:49:59 -07:00
bbf8f76823
GraphQL: Implement scalar ( #2313 )
2017-06-27 19:34:25 -07:00
0a2a099efe
GraphQL: Implement interface ( #2312 )
2017-06-27 19:30:58 -07:00
8e31088761
GraphQL: Implement input ( #2311 )
2017-06-27 19:27:02 -07:00
b63e1c2dd7
GraphQL: Implement Enum ( #2310 )
2017-06-27 19:20:53 -07:00
51c7503dae
GraphQL: Implement DirectiveDefinition ( #2309 )
2017-06-27 19:10:07 -07:00
fbf4c3a952
GraphQL: Support object definition implements ( #2307 )
2017-06-27 18:51:56 -07:00
ee07ff5870
Fix master
2017-06-27 18:33:23 -07:00
af309e3acd
Add support for GraphQL TypeExtensionDefinition ( #2306 )
2017-06-27 18:26:43 -07:00
f96fe1ea5e
Initial support for GraphQL ObjectTypeDefinition ( #2305 )
...
It appears in some files inside of fb codebase
2017-06-27 18:22:04 -07:00
189027c7d3
GraphQL: Use spaces instead of commas ( #2303 )
...
"Daniel Schafer: Yeah, that's definitely what I'd describe as the canonical style; anytime you have two "things" on a line, use commas, but if you have a newline it's not needed."
2017-06-27 18:13:07 -07:00
4d46a3975b
GraphQL: Remove circular dependency in ast ( #2304 )
...
The tokens are attached to the location via the prototype (so they are not visible when you JSON.stringify) but the various places where we traverse the ast see them. It causes stack overflows and comments that are not printed because they are attached to tokens instead of real nodes.
Fixes #2302
2017-06-27 18:12:30 -07:00
850d51a033
Tweak name
2017-06-27 17:30:13 -07:00
b47c0b4e04
Allow formatting ranges of JSON ( #2298 )
...
* Add test for https://github.com/prettier/prettier/issues/2297
* Add JSON types to isSourceElement()
See https://github.com/prettier/prettier/issues/2297
* Avoid expanding format range when possible
This fixes https://github.com/prettier/prettier/issues/2297
* Move JSON range test into tests/range_json
This is so that the AST_COMPARE=1 tests don't try to parse JSON with Flow.
* Check parser in isSourceElement()
Otherwise JSON formatting would format weird things inside of JS.
See https://github.com/prettier/prettier/pull/2298#discussion_r124407056
* Use arrow functions instead of .bind()
See https://github.com/prettier/prettier/pull/2298#discussion_r124409783
* Add test of range-formatting JSON identifier
See https://github.com/prettier/prettier/pull/2298/files#r124410750
* Allow range-formatting JSON identifier
See https://github.com/prettier/prettier/pull/2298/files#r124410750
* Fix lint
2017-06-27 16:04:42 -07:00
5f063ab168
Fix locEnd() for postcss parser ( #2295 )
...
* Fix locEnd() for postcss parser
`node.source` doesn't have an `end`, but `node.nodes[-1].source` does.
Fixes https://github.com/prettier/prettier/issues/2267
* Add regression test for https://github.com/prettier/prettier/issues/2267
See https://github.com/prettier/prettier/pull/2295#issuecomment-311484343
* Make locEnd() postcss fix more focused
This passes the tests again.
* Use getLast() instead of .slice()
See https://github.com/prettier/prettier/pull/2295#discussion_r124398553
* Move CSS range test into tests/range_css
This is so that the AST_COMPARE=1 tests don't try to parse CSS with Flow.
2017-06-27 15:12:22 -07:00
adc71ef6ae
1.5.1
2017-06-27 13:42:31 -07:00
6f4eade422
Go back to babylon beta 13 ( #2289 )
...
Fixes #2286
2017-06-27 11:51:23 -07:00
073a2071a8
Inline import('x') to avoid having trailing , ( #2288 )
...
Fixes #2287
2017-06-27 11:40:20 -07:00
5e51caca1b
Add GraphQL to README ( #2265 )
...
* Add GraphQL to README
* Add JSON to main list of languages
2017-06-27 10:18:22 -07:00
500cf98c06
1.5.0
2017-06-27 10:09:59 -07:00
b257c68772
Use perl instead of sed for replacing eval
2017-06-27 10:02:31 -07:00
803b7ff6b9
Add \n at the end of .graphql files ( #2285 )
...
We need to use the same hack as CSS unfortunately.
Fixes #2275
2017-06-27 09:49:15 -07:00
1e48f34ac8
Copy README.md to the dist/ folder ( #2284 )
...
Fixes #2275
2017-06-27 09:48:06 -07:00
e707bdd52f
Print comments attached to {' '} ( #2283 )
...
We had two occurrences on fb codebase where people attached comments on `{' '}` which would be swallowed. Instead of dropping the comments, let's make the algorithm a bit less naive.
2017-06-27 09:35:03 -07:00
6017ac13c7
Create CNAME
2017-06-27 07:43:54 -07:00
be600337eb
Improve JSX output when there is a single expression ( #2274 )
2017-06-26 19:05:34 -07:00
95a5f11be9
Tweak to support FB translation pipeline ( #2272 )
...
This also improves formatting when there are consecutive tag/expression elements with no white space between them.
2017-06-26 09:30:52 -07:00
174bbda7ef
Minor readme cleanups
2017-06-26 17:42:28 +02:00
fe7fb260a4
Fix a case where significant whitespace was dropped ( #2270 )
2017-06-26 03:03:13 -07:00
400f34624f
Add module, class and typed nodes to sourceElements ( #2266 )
...
babylon flow typescript parsers
+ tests to cover module and class
2017-06-25 09:07:52 -07:00
b8af5e5241
Update URL in atom.md
2017-06-25 14:24:05 +10:00
caa77fbfe8
Join range start and range end documentation
2017-06-25 12:44:18 +10:00
9a55f5b2d6
Fix unstable arrow comments ( #2262 )
...
It outputted which is completely wrong
```js
<FlatList
renderItem={info => <span>{info.item.widget.missingProp // $FlowExpectedError - bad widgetCount type 6, should be Object
}</span>}
/>;
```
2017-06-25 12:30:09 +10:00
438f5887e2
Add links to prettier's parsers
...
Since the parser API exposes the AST, it makes sense to point people towards the parsers we use so they can hack on them.
2017-06-25 12:27:49 +10:00
f71fcd0b65
Fix variance location ( #2261 )
...
Turns out when we refactored for TS, we moved it before "static" and it no longer parses. Oops.
2017-06-25 11:46:29 +10:00
38d4661ba9
Forward originalText in multiparser ( #2260 )
...
If we don't, all the places where we read from the original text (mostly comments) are reading into random places.
Fixes #2258
2017-06-24 17:54:09 -07:00
Simone Picciani