$ the-wire · showcase
STYLE GUIDE GETS VUE 3 OVERHAUL AS LANGUAGE TOOLS FIXES COMPLETION BUGS
By RepoJournal · Filed · About Vue.js · Composed from the cited sources · methodology
1 person shipped this
Vue's official style guide is finally shedding its Vue 2 skin, while the language tools team ships a batch of IDE fixes that should make your template completion stop lying to you.
The docs team moved the style guide to a Vue 3 baseline [1], clearing out years of stale guidance and removing the deprecation banner that's been haunting the docs. This is the foundation work that needed to happen before major style guide improvements could land without requiring a total rewrite. Meanwhile, the language-tools desk shipped five targeted fixes across the stack [2][3][4][5][6]. The completion engine was double-requesting attributes and props in some cases, TypeScript plugin was returning component props when it shouldn't, and boolean attribute completions were adding unnecessary empty strings to your templates. The most subtle fix: v-if branch fragments now get properly traversed when collecting root nodes, which means template validation stops throwing false positives on conditional roots.
Action items
- → Review your style guide bookmarks - the Vue 3 baseline is now canonical vuejs/docs [plan]
- → Update language-tools and IDE extensions to pick up completion fixes vuejs/language-tools [monitor]
References
- [1] docs: update style guide to a vue 3 baseline ↗ vuejs/docs
- [2] fix(language-service): reset to default data provider after running with vue data provider ↗ vuejs/language-tools
- [3] fix(language-service): strip `=""` only for plain boolean props completion edits ↗ vuejs/language-tools
- [4] fix(typescript-plugin): only return props when completion target is component node ↗ vuejs/language-tools
- [5] fix(language-service): avoid duplicate attrs and props requests ↗ vuejs/language-tools
- [6] fix(language-core): penetrate `v-if` branch fragments when collecting single root nodes ↗ vuejs/language-tools
