Conversation
|
|
||
| ```js | ||
| ifBreak(";", " ") | ||
| ifBreak(";", " "); |
There was a problem hiding this comment.
Hmm, these are kind of expressions. Not statements, which is probably why there wasn't a semicolon here. Not the end of the world, I guess.
| Copy the following config into your `.pre-commit-config.yaml` file: | ||
|
|
||
| ```yaml | ||
|
|
There was a problem hiding this comment.
No, the leading/trailing new line does nothing there.
| <summary><strong>Table of Contents</strong></summary> | ||
|
|
||
| - [Vim and Prettier integration](#vim-and-prettier-integration) | ||
| * [Neoformat](#neoformat) |
There was a problem hiding this comment.
This is autogenerated so should be ignored.
| vim-prettier executable resolution: | ||
|
|
||
| 1. Tranverse parents and search for Prettier installation inside `node_modules` | ||
| 2. Look for a global prettier installation |
There was a problem hiding this comment.
I still think we should preserve this choice @ikatyang
There was a problem hiding this comment.
Should we add an option for it? or just print ordered numbers if the second number equals the first number +1?
EDIT: auto-detection should be better.
There was a problem hiding this comment.
I'd say a good enough heuristic could be always use 1. iff items[1].number === "1.".
| Include this anywhere to force all parent groups to break. See `group` for more | ||
| info. Example: | ||
|
|
||
| ```js |
There was a problem hiding this comment.
fixed.. maybe you can delete this comment so it won't confuse us
|
|
||
| will output | ||
|
|
||
| ```js |
|
|
||
| and **not** | ||
|
|
||
| ```js |
|
|
||
| For example: | ||
|
|
||
| ```js |
|
|
||
| [link](https://github.com/prettier/prettier/compare/1.7.3...1.7.4) | ||
|
|
||
| * Force template literals to break after \` for styled-components (#2926 by duailibe) |
There was a problem hiding this comment.
@ikatyang Should we pick * as unordered list instead?
There was a problem hiding this comment.
I think we should do some research for this too, just like the decision we made for strong/emphasis.
azz
left a comment
There was a problem hiding this comment.
Looks good. As you mentioned there are a handful of places we want to ignore.
| ## Configure External Tool | ||
|
|
||
| https://blog.jetbrains.com/webstorm/2016/08/using-external-tools/ | ||
| [https://blog.jetbrains.com/webstorm/2016/08/using-external-tools/](https://blog.jetbrains.com/webstorm/2016/08/using-external-tools/) |
There was a problem hiding this comment.
This is a bug, we should print it with shortcut-style, i.e. <https://...>, opened #3030.
…ettier/md * 'master' of https://github.com/prettier/prettier: feat(cli): add `--loglevel` option (prettier#2992)
|
also I'm not sure how to incorporate markdown with the precommit hook.. but maybe we can do that after the official release.. |
|
@lipis there have been some changes to Markdown since you opened this PR. Did you want to re-run this with the current |
|
yes I will do that once I'll get in front of my computer.. |
|
should I fix anything else? |
|
Yes, we need to figure out how to fix the "TOC should be up-to-date" test (which currently causes Travis to fail). |
|
Would this work? <!-- prettier-ignore -->
<details>
... |
|
would be nice.. html support is coming soon as well as it looks like ;) |
| For example: | ||
|
|
||
| ```js | ||
| matrix( |
There was a problem hiding this comment.
This block need to be <-- prettier-ignore -->d.
| JSON: | ||
|
|
||
| ```json | ||
| // .prettierrc |
There was a problem hiding this comment.
We don't want this comment to move. Perhaps <!-- prettier-ignore --> this too.
editors/atom.md
Outdated
| @@ -1 +1,2 @@ | |||
| See https://github.com/prettier/prettier-atom | |||
| See | |||
| [https://github.com/prettier/prettier-atom](https://github.com/prettier/prettier-atom) | |||
…ettier/md * 'master' of https://github.com/prettier/prettier: Fix util.getStringWidth for falsy input (prettier#3092)
|
Updated.. the following didn't work.. so I rerun the |
README.md
Outdated
| For example: | ||
|
|
||
| ```js | ||
| matrix(1, 0, 0, 0, 1, 0, 0, 0, 1); |
There was a problem hiding this comment.
The ignore comment needs to be above the fence otherwise it will show up in the rendered version.
| ```json | ||
| { | ||
| <!-- prettier-ignore --> | ||
| // .prettierrc |
There was a problem hiding this comment.
Same here. Ignore needs to move above ```json
|
I think it's ready |
|
I think it'd be better to wait for the 1.8 release (or use current |
|
Makes sense! |
|
I think I will close that.. but the issue still remains.. we need to format all the md files with Prettier.. and use hooks for the future ones.. |
Some of the JS examples though must be ignored.
Let me know what would be the default print size and I'll edit the JS examples that needs to be reverted and not prettified.