Open in Stackblitz

pnpm add https://pkg.pr.new/vuejs/language-tools/vue-component-meta@4971

pnpm add https://pkg.pr.new/vuejs/language-tools/vue-component-type-helpers@4971

pnpm add https://pkg.pr.new/vuejs/language-tools/@vue/language-plugin-pug@4971

pnpm add https://pkg.pr.new/vuejs/language-tools/@vue/language-core@4971

pnpm add https://pkg.pr.new/vuejs/language-tools/@vue/language-server@4971

pnpm add https://pkg.pr.new/vuejs/language-tools/@vue/language-service@4971

pnpm add https://pkg.pr.new/vuejs/language-tools/vue-tsc@4971

pnpm add https://pkg.pr.new/vuejs/language-tools/@vue/typescript-plugin@4971

commit: 63c4f50

I think writing types in v-generic is wrong in Vue's specification, according to the documentation custom directives only receive JS statements, the v-generic convention may break compatibility with other tools/libraries.

We should use generic, or convention to pass type parameters in HTML comment through <!-- @vue-generic {xxx} -->.

The runtime support for v-generic only requires the use of noopDirectiveTransform to skip the compile of this directive vuejs/core#12301, which should only cause the user's custom directive with the same name to become invalid.

@KazariEX I see, but this will still break Vue versions prior to vuejs/core#12301, especially since Vue 2 has stopped being maintained. Since this is a language tools specific feature, we need an implementation that doesn't have to change core.