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
Default views generated from scaffolding, does client side validation on fields based on the constraints defined in the domain class.
It could be a common practice, that on the update page, if a user left any of the fields empty, the behaviour should be to update all fields except those left empty.
Why these field names are not passed as parameters to the generate-all script?. This seems logical requirement and could be included in the framework and would save development time. Giving that is is applied only to modify page, (Not to create page for example).
Regards,
The text was updated successfully, but these errors were encountered:
Hi,
Default views generated from scaffolding, does client side validation on fields based on the constraints defined in the domain class.
It could be a common practice, that on the update page, if a user left any of the fields empty, the behaviour should be to update all fields except those left empty.
Why these field names are not passed as parameters to the generate-all script?. This seems logical requirement and could be included in the framework and would save development time. Giving that is is applied only to modify page, (Not to create page for example).
Regards,
The text was updated successfully, but these errors were encountered: