[MGNLCT-168] required property included in complex fields by default Created: 23/Dec/20  Updated: 19/May/21  Resolved: 19/May/21

Status: Closed
Project: Content Types
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Mercedes Iruela Assignee: Milan Divilek
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
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:
Epic Link: Support for required property
Sprint: UI FW 27, UI FW 28
Story Points: 3

 Description   

Steps to reproduce

  1.  Create a content app using a content-type, this content app should include complex fields such us composite or multivalue fields. (example).
  2.  Go to Definitions app and see some MINOR issues related to some default properties not supported by the new UI, such as, required property in complex fields (which is not allowed, see MGNLUI-6239).

Expected results

No problems reported in Definitions app

Actual results

Errors reported in definitions app, like:

Property [required] not found in class [info.magnolia.ui.field.CompositeFieldDefinition], property is not assigned

Title: Source data processing problem
Path: destinations/subApps/detail/form/{name=name, i18n=false, required=true, $type=textField, type=java.lang.String, validators={0={$type=nodeNameValidator, name=0}}}/portraitImage

Workaround

-

Development notes

Seems to be included y detailTemplate.https://git.magnolia-cms.com/projects/PLATFORM/repos/ui/browse/magnolia-ui-framework-jcr/src/main/resources/contenttypes/detailTemplate.ftl

it happens also with some other properties that are included by default but not supported by some fields.

The most straightforward solution would be skipping required property for complex fields when generating the app.



 Comments   
Comment by Milan Divilek [ 19/May/21 ]

This issue is caused by missing submodel definition for complex fields in content-types definition.

Generated at Mon Feb 12 00:37:48 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.