better integration of bv-groups
Open
Nobody has claimed this yet.
Component: Validation/Conversion
Priority: Major
Type: Improvement
- Dominant language
- Java
- Stars
- 127
- Forks
- 59
- Avg merge
- 23h
- Merged PRs (30d)
- 7
Description
in several cases different bv-groups should get used (in the validation-phase) depending on the triggered action.
(if there are e.g. multiple buttons in the same form which should lead to different bv-constraints.)
also see: https://issues.apache.org/jira/browse/EXTVAL-141
Affected Versions
[2.2]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading this issue and the linked EXTVAL-141 discussion, then trace how Jakarta Faces selects validation groups during the validation phase. Clarify how the triggered action should determine the applicable bv-groups and define completion as supporting different constraints for multiple buttons in one form.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100