Details
-
Bug
-
Resolution: Not an issue
-
Normal
-
None
-
None
-
None
-
Empty show more show less
-
UI FW 27, UI FW 28
-
3
Description
Steps to reproduce
- Create a content app using a content-type, this content app should include complex fields such us composite or multivalue fields. (example).
- 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.
Checklists
Acceptance criteria