-
-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for 'prettier-standard-formatter' #20
Comments
Hi @alex-shamshurin, Sorry but the goal of this project is to add support and evolve together with https://github.com/prettier/prettier |
I understand that, but I'd like make a little post-processing, pipe the output to |
Hi @alex-shamshurin, Its not a policy/restriction, however at this stage our main focus is on prettier. I am happy to revisit this issue if there is enough interest around that in the future. Once again thank you for submitting this request and I am sorry that at this stage we won't be able to action on it. |
Since there has been some more interest on supporting other CLI's (#42) I am now re-opening this issue. |
Still interested on working in this issue, will prioritize bumping vim-prettier to support the new prettier 1.6 features then get back to this issue |
Does vim-prettifier need some changes to support 1.6? As I read it just formatting a bit different.. |
Prettier 1.6 adds support for user defined custom configuration, I want to think what would be the best way to integrate that feature in here |
I think project .prettierrc file must have the highest priority and only then .vimrc |
Do people still think its worth integrating with other CLI's ? or is the prettier configuration settings via .prettierrc enough these days ? |
This is same as #148 |
I'd like to use it both. If there are an option to specify which tool to be used?
The text was updated successfully, but these errors were encountered: