[MGNLUI-3844] MultiValueField's validation is not concrete Created: 11/Apr/16  Updated: 23/Oct/17  Resolved: 14/Apr/16

Status: Closed
Project: Magnolia UI
Component/s: dialogs
Affects Version/s: 5.4.4
Fix Version/s: 5.4.6

Type: Bug Priority: Neutral
Reporter: Michael Mühlebach Assignee: Ilgun Ilgun
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: 0d
Time Spent: 1d
Original Estimate: Not Specified

Attachments: File case5.yaml    
Issue Links:
Relates
relates to CONTEDIT-135 Highlight field group in case of vali... Closed
dependency
relation
is related to MGNLUI-3668 MultiValueFields must react on the ch... Closed
is related to MGNLUI-3793 Explore notification of validation er... 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
Sprint: Basel 39
Story Points: 2

 Description   

MultiValueField has a CompositeField and this CompositeField has one SwitchableField with two inner required fields - the error is thrown dialog wide, hiding what's missing actually. Only re-rendering the dialog causes the error message to be propagated to given field.

After some investigation found out that actually, MultiValueField's validation is the cause of the problem since even only with basic TextField its validation is not showing what went wrong until a refresh of the page.


Generated at Mon Feb 12 09:10:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.