This isn't really much of a problem: complete support for HTML and Vue is planned for Prettier 1.15! ๐๐๐ And to me, it looks really good. See prettier/prettier#5259 for their progress and a link to a preview.
This issue is to hopefully begin implementing opt-in support for these changes so that Vetur will be ready once the new version of Prettier is released.
However, IMHO, the best way to do this is a bit different: once Prettier 1.15 is released, one solution is to simply disable formatting by default, and encourage users to install the official Prettier VS Code extension alongside Vetur. This way, Vetur should still support language-specific formatters for individual script/style/template blocks (ESLint, TSLint, stylus-supremacy, etc.) but users could also switch to using their own language-agnostic, whole-file/unified formatting with Prettier. I think that users can still opt to only format certain languages in Vue files.
This approach has many benefits:
Overall, decoupling Prettier from Vetur will soon be made possible, which is a good change for users and developers alike.
Side note: this may impact (or maybe fix) #543.
Airkro, andylima, jennale, sirhcm, staskorz and 22 moreAirkro and ThomOrloAirkro, ThomOrlo and mustafakibar
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4