vNode hooks are not triggering if a component does not have any props declared

[CyberAP]

Version

3.0.0-alpha.4

Reproduction link

JSFiddle

Steps to reproduce

1. Define a component with no props
2. Use that component as a child of another component
3. Set up some action on vNode hook, for example: @vnodeMounted="onMounted"
4. Hook is not triggering until child component has any props declared

What is expected?

Hooks should be working without declaring any props

[yyx990803]

Hmm, maybe we should rename the vnodeXXX hooks to elementXXX, since they are actually designed for working with DOM elements (and is the underlying mechanism for directives).

When used on a component, they are passed down to the component as part of $attrs, and automatically spread on to the child component root when the child component has declared props. This is what enables usage of a directive on a component - e.g. <Foo v-show="ok"/>.

The thing to note here is that a component with optional props doesn't perform the auto-spread behavior. I think this could be confusing so we may want to rethink that behavior.

[CyberAP]

I personally would find it very useful for hooks to not contain any information of what they are related to and use them directly, like this:

<FooBar @mounted="onFooBarMounted" />

This goes on par with the component options and does not conflict with them since they're prefixed with on.

I don't know much about native vue renderers, but I'm pretty sure there's no such concept as element there.