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
We're currently handling custom components the following way:
A custom component is passed to Resource by a user
Resource injects a va props into this component with crud functionality
The user accesses it's props to use the crud functions, like this.va.fetchList
Gabi Buenou (aka @glmaljkovich) suggested mixins to inject this functionality. This would not only provide a facility to the user (usage be like: $va.fetchList), but would also help decoupling the binding utils from the resource utils: more information in this WIP
The text was updated successfully, but these errors were encountered:
We're currently handling custom components the following way:
this.va.fetchList
Gabi Buenou (aka @glmaljkovich) suggested mixins to inject this functionality. This would not only provide a facility to the user (usage be like:
$va.fetchList
), but would also help decoupling the binding utils from the resource utils: more information in this WIPThe text was updated successfully, but these errors were encountered: