Custom Directive API Change

[yyx990803]

• Re-design custom directive API so that it better aligns with component lifecycle

• Custom directives usage on components will follow the same rules as discussed in the Attribute Fallthrough Behavior RFC. It will be controlled by the child component via v-bind="$attrs".

Rendered

[zhangenming]

this will be better?

componentUpdated -> removed ,use updated instead

[Gnuk]

@zhangenming, I think it's the same case as bind -> beforeMount, inserted -> mounted and unbind -> unmounted, so this suggestion may not be needed for me.

[ycmjason]

is there any ways to incorporate setup() and reactivity in custom directive? or will it not serve the purpose of directives?

[yyx990803]

This RFC is now in final comments stage. An RFC in final comments stage means that:

The core team has reviewed the feedback and reached consensus about the general direction of the RFC and believe that this RFC is a worthwhile addition to the framework.
Final comments stage does not mean the RFC's design details are final - we may still tweak the details as we implement it and discover new technical insights or constraints. It may even be further adjusted based on user feedback after it lands in an alpha/beta release.
If no major objections with solid supporting arguments have been presented after a week, the RFC will be merged and become an active RFC.