Thanks for this update, custom directives IntelliSense and Type-Checking is coming!

We also needComponentCustomComponents (global components). Similar toJSX.IntrinsicElements but actually it's use for handle different problem.

We also need ComponentCustomComponents (global components). Similar to JSX.IntrinsicElements but actually it's use for handle different problem.

@johnsoncodehkI think this is worth putting in a new issue for tracking, with as detailed information as possible. 😁

Edit: After reviewing the code, I think it can be implemented in this PR if possible

We also needComponentCustomComponents (global components).

Maybe a better name would be good, any suggestions?

GlobalComponents andGlobalDirectives?

GlobalComponents andGlobalDirectives?

Look good, but inconsistent...

declare module'vue'{interfaceComponentCustomOptions{}interfaceComponentCustomProperties{}interfaceGlobalComponents{}interfaceGlobalDirectives{}}

Look good, but inconsistent...

It looks inconsistent but they mean different things

• ComponentCustomOptions : Component custom options when youdefineComponent, eg:onBeforeRouteUpdate
• ComponentCustomProperties : Customvm properties available on thecomponentInstance, eg:$router
• GlobalComponents : Components added to theapp/global, available on every component (render), eg:router-view
• GlobalDirectives : Directives defined to theapp/global, available on every component (render), eg:v-tooltip

As you can see they usually mean different things, altho the Components/Directives are used on the components, they are not enhancing the component interaction, but to provide enhancement to the render.

I mean this is my logic on the naming, might be incorrect 😄

HavingComponentCustomComponents sounds a bit bad 😆

yeah, they are different.

/ecosystem-ci run

Can this be merged?

Note, one thing I figured out you can do is simply use TypeScript'ssatisfies to get type-checking for custom directives. For example:

<divv-popover="{    html:true,    title:vm.tooltipTitle(),    placement:'right',    trigger:'click',    content:vm.tooltipContent()    }satisfiesPopoverOptions"></div>

Volar's code syntax coloring ofVue files completely borks if you usesatisfies in that way, but it looks like the technique itself succeeds.

It would be great if there was an ESLint plugin then to force / enforce the use ofsatisfies for any custom directive in the meantime (I guess from theeslint-plugin-vue folks) but that's a separate issue.

/ecosystem-ci run

📝 Ran ecosystem CI:Open