[MGNLUI-2381] Composite field validators ignored Created: 12/Nov/13  Updated: 22/Jul/14  Resolved: 22/Jul/14

Status: Closed
Project: Magnolia UI
Component/s: app framework
Affects Version/s: 5.1.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Marek Swiecznik Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-2871 Enhance the behavior of complex fields Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Every field can have a validator, so I expect that composite field can have too.

In an editor subapp, composite field validators are created, but isValid is never called, even on save (commit).

Field configuration:

+ someCompositeField
+ + fields
+ + + dateFrom
+ + + + (...)
+ + + dateTo
+ + + + (...)
+ + validators
+ + + startBeforeEndValidator
+ + + + (...)
+ + class info.magnolia.ui.form.field.definition.CompositeFieldDefinition



 Comments   
Comment by Eric Hechinger [ 22/Jul/14 ]

obsolete since 5.2.5

Generated at Mon Feb 12 08:56:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.