Functional proposal for custom components rendering about vue-admin HOT 4 CLOSED

@sebastianlp thanks for sharing your idea :) I edited the title a little bit so that we understand what we will be dealing with in this issue. I'll be taking a look as soon as I can!

from vue-admin.

If I can help with something, share thoughts, discuss, whatever, contact me!

from vue-admin.

I used this issue and the information provided to start an experimental implementation using functional rendering.
I first created a custom component as a user and tried to wrap key form elements, such as inputs and buttons, with some sort of core wannabe components, hoping I could then inject functionality into the native ones chosen by the user (v-text-field, v-btn, from vuetify, etc...). Diving for their children to inject functions on click or input/change events didn't seem to be as easy as I thought, though it doesn't seem to be impossible to implement, but a little dirty. I left a few Vue functional components to keep experimenting, that can work as wrappers for other components provided by a user.
I figured we can pass vue components as props to our Resource core component. All this work led me to build a simple and dynamic api that is kind of injected into components provided by a user for a specific view, Create for example. This approach continues in #42

from vue-admin.

Now that #42 is merged, we're ready to think about functional rendering on those built-in components Vue-Admin will automatically provide when declaring a Resource instance.

Closing this and continues in #72

from vue-admin.