Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Mixin proposal for resource components injected with va prop #52

Open
sgobotta opened this issue Jan 8, 2019 · 0 comments
Open

Mixin proposal for resource components injected with va prop #52

sgobotta opened this issue Jan 8, 2019 · 0 comments
Labels
investigate Frequently related to functionality investigation or testing tasks proposal ideas, functional features, etc

Comments

@sgobotta
Copy link
Member

sgobotta commented Jan 8, 2019

We're currently handling custom components the following way:

  1. A custom component is passed to Resource by a user
  2. Resource injects a va props into this component with crud functionality
  3. 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
@sgobotta sgobotta added the investigate Frequently related to functionality investigation or testing tasks label Jan 8, 2019
@sgobotta sgobotta added the proposal ideas, functional features, etc label Jan 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
investigate Frequently related to functionality investigation or testing tasks proposal ideas, functional features, etc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sgobotta