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
The main issue is the amount of Vue (and JS) code one would need to write (see https://github.com/matrei/pingcrm-grails ) in order to achieve that level of functionality (compared to a dynamically ~80% + statically ~20% scaffolded "classical" Grails web app).
The huge amount of code is of course mainly an issue "imported" by Vue (same problem with React, Angular, etc) because of the extremely high verbosity (Inertia does not seem add that much).
If the templates could also be installed in the application with install-templates for small tuning (like it's possible now with the default web profile) than there would be zero practical reason not to use this plugin, since this would not cause much more work for any Grails Project 😃 .
IMO a "new profile" is not really needed, since the "setup" for a project is done only once (e.g. using plug-ins like Spring Security, Audit, etc also do not require a different profile, but they just extend the scaffolding and commands)
Thank you !
The text was updated successfully, but these errors were encountered:
Hi @aadrian, I think your are right. It would be useful to be able to call something like inertia-vue3-quickstart and get a working VueJS/Inertia project set up. I'll look into it. 👍
Hi,
Please add Vue Scaffolding Templates !
See earlier discussion here: matrei/pingcrm-grails#1 .
The main issue is the amount of Vue (and JS) code one would need to write (see https://github.com/matrei/pingcrm-grails ) in order to achieve that level of functionality (compared to a dynamically ~80% + statically ~20% scaffolded "classical" Grails web app).
The huge amount of code is of course mainly an issue "imported" by Vue (same problem with React, Angular, etc) because of the extremely high verbosity (Inertia does not seem add that much).
If the templates could also be installed in the application with
install-templates
for small tuning (like it's possible now with the default web profile) than there would be zero practical reason not to use this plugin, since this would not cause much more work for any Grails Project 😃 .IMO a "new profile" is not really needed, since the "setup" for a project is done only once (e.g. using plug-ins like Spring Security, Audit, etc also do not require a different profile, but they just extend the scaffolding and commands)
Thank you !
The text was updated successfully, but these errors were encountered: