-
-
Notifications
You must be signed in to change notification settings - Fork 3
Support writing components as Vue files #19
base: master
Are you sure you want to change the base?
Conversation
@rstoenescu do you see any other problems supporting Vue files for UI extensions? This PR has worked for all my UI extensions which are all written as Vue files. 😉 |
fixed merge conflicts |
fixed new merge conflicts @rstoenescu any chance this can get merged? Your feedback is much appreciated! |
Would love to see this in the ui kit! my use case is creating a simple, default login form to go with a Laravel Sanctum login extension. |
Any updates on this? |
We would just have to make it clear in the docs, that render functions should be used where possible because they're
|
I think those statements are opinions not facts. Something is only as flexible as a developers imagination, and a more difficult to read format can lead to a higher difficulty and limiting the developer's creativity therefore being less flexible. When it comes to ease of debugging usually the most important thing is code readbility, which I argue is higher with Vue files as well.... |
@mesqueeb These thoughts are not my own, was parroting what I've heard in the quasar community. @hawkeye64 what are your thoughts? Our use case for quasar extensions, is organizing components across applications (we have several small PWAs). We plan to create full login flows so that this logic remains dry by using app extensions. Creating a full login page without SFCs doesn't feel right. That's our use case for wanting SFCs, and I imagine similar use cases may become more common. |
@ldiebold Create a new UI kit project. Add the appropriate SFC handling. Add to github and mark as template. Use as necessary. |
fixes #18