You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 14, 2020. It is now read-only.
It would be great if getInitialData could be pulled from mixins. For now, I have to copy/paste this to every component that needs to reuse getInitialData:
it would be also great if this inside getInitialData pointed to the component for which it is called (not the vm which is non-existent at the moment of that call, but the component options). That would allow to have several components extending a single mixin, and then refer to specific component's options from the common getInitialData coming from a mixin. (Alternatively, component may be added to context).
The text was updated successfully, but these errors were encountered:
It would be great if
getInitialData
could be pulled from mixins. For now, I have to copy/paste this to every component that needs to reusegetInitialData
:it would be also great if
this
insidegetInitialData
pointed to the component for which it is called (not thevm
which is non-existent at the moment of that call, but the component options). That would allow to have several components extending a single mixin, and then refer to specific component's options from the commongetInitialData
coming from a mixin. (Alternatively,component
may be added tocontext
).The text was updated successfully, but these errors were encountered: