apache / apache/grails-core

Validation Suggestions - Partial/Select Validation

Open
#14,295 0 comments 0 reactions 0 assignees View on GitHub
relates-to: scaffolding
Dominant language
Groovy
Stars
2.9k
Forks
975
Avg merge
1d 22h
Merged PRs (30d)
92

Description

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,

Contributor guide

Open the contributing guide

Research direction

The issue names generated scaffold views, domain-class constraints, client-side validation, and the generate-all script, but no files or tests. Start by locating the scaffolding and validation-generation entry points, then clarify how empty update fields should be distinguished from create-page fields. Done means the intended partial-update behavior is specified and covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
groovy
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.