[MGNLUI-6112] RichTextField and CodeField ignore required flag Created: 04/Aug/20  Updated: 20/Aug/20  Resolved: 14/Aug/20

Status: Closed
Project: Magnolia UI
Component/s: dialogs
Affects Version/s: 6.2.2
Fix Version/s: 6.2.3

Type: Bug Priority: Critical
Reporter: Chris Jennings Assignee: Adam Siska
Resolution: Fixed Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causality
relation
is related to MGNLUI-6114 RichTextField validators showing erro... Open
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
Release notes required:
Yes
Date of First Response:
Epic Link: UI framework implementation
Sprint: Maintenance 19, Maintenance 20
Story Points: 5

 Description   

When configured with "required: true", a rich text field ignores the flag and can be saved when empty.
The required property and its value are visible in the Definitions app and the JCR shows no value is saved.

Dev notes:
code field has very similar symptoms

Steps to reproduce:
1) use both codeField and richTextField  in detail/dialog
2) open detail/dialog
3) commit/save without any touch
4) add/remove some chars in code field (leave it blank)
4) commit/save

Expected:
both field should have validation error in step 3 and 5.

Actual:
only code field has validation error in step 3, no field has validation error in step 5

 



 Comments   
Comment by Chris Jennings [ 04/Aug/20 ]

Customer reported issue.

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