4af3dd4b07
test: improve snapshots ( #5521 )
...
- before
```
${input}${"~".repeat(printWidth)}
${output}
```
- after
```
===options===
${options}
${" ".repeat(printWidth)}| printWidth
====input====
${input}
===output====
${output}
=============
```
2018-11-25 16:21:14 +08:00
51b7c02e12
Upgrade jest to 22 ( #4782 )
...
* chore: upgrade Jest
* chore: update snapshots
* chore: lock down babel dependency using invalid syntax
* 2 args to test.skip
* use jest 22 for now
* Revert "2 args to test.skip"
This reverts commit 691fdc3f99e320f2303958f2b503f7b4c93fa455.
* remove snapshot name from matcher
* fix standalone tests skips
2018-07-03 03:06:29 -03:00
a05fd118be
Do not require space after markdown block language name ( #4783 )
...
https://github.com/prettier/prettier/pull/4153 made it possible to detect fenced code block language when it is followed by arguments (e.g. ` ```js {something=something} `). This PR makes it also possible to detect language in cases cases like ` ```js{something=something} ` (no space).
The reason for this change is that Atom highlights code blocks regardless of a space after the language name, which makes users wonder why the correctly detected code block is not being formatted:
<img width="324" alt="screen shot 2018-06-28 at 22 08 13" src="https://user-images.githubusercontent.com/608862/42060780-db11f5b6-7b1f-11e8-9f43-fe91843f7d89.png ">
PR background: https://github.com/prettier/prettier/pull/4153#issuecomment-401174999
2018-07-02 08:22:56 +08:00
0c09e150ba
feat(markdown): support fenced codeblock lang followed by attributes ( #4153 )
...
* test: add tests
* feat(markdown): support fenced codeblock lang followed by attributes
ref: https://shd101wyy.github.io/markdown-preview-enhanced/#/code-chunk
* refactor: set limit
2018-03-16 00:25:39 +08:00
2b283908cf
fix(markdown): print literalline for newline instead of hardline ( #4083 )
...
* test: add tests
* fix(markdown): print literalline for newline instead of hardline
* test: add tests
2018-03-01 14:42:20 +02:00
829616dd6c
Fix multiparser trailing comma regression ( #3405 )
...
* Fix multiparser trailing comma regression
* Refactor trailing comma application
2017-12-05 19:01:00 +01:00
Ika
