[MGNLUI-829] Field with property extends=override should not create a FieldDefinition Created: 06/Mar/13  Updated: 24/May/16  Resolved: 24/May/16

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.0
Fix Version/s: None

Type: Task Priority: Major
Reporter: Eric Hechinger Assignee: Eric Hechinger
Resolution: Outdated Votes: 0
Labels: dialog, form
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-2165 Decored FieldDefinition can no more u... Closed
relation
is related to MGNLUI-819 Creating a new "Promo" component rais... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Until Magnolia 4.5 a field definition like :
/modules/standard-templating-kit/dialogs50/components/promos/stkPromo/formDefinition/tabs/tabTeaser/fields/hideTeaserImage
didn't generate a field but was used to remove the equivalent field form the extrended dialog:
Let say that you have

dialogs/a/form/tabs/tab/
with
field1
field2
field3

and
dialogs/b/form/tabs/tab/
extends = dialogs/a/form/tabs/tab/
with
field2
extends = override

In this case, the dialog b would have the field1 and field3.

field2
extends = override
is used to exclude the field from the extend.

Now with magnolia 5 this field is mapped to a ConfiguredFieldDefinition and this class has no real field implementation.

Currently in this case Node2BeanTransformerImpl.resolveType define that this node is a 'field', field is mapped to info.magnolia.ui.model.field.definition.FieldDefinition and based on the type mapping of the ui-admincentral.xml file
<type-mapping>
<type>info.magnolia.ui.model.field.definition.FieldDefinition</type>
<implementation>info.magnolia.ui.model.field.definition.ConfiguredFieldDefinition</implementation>
</type-mapping>
mapp to a ConfiguredFieldDefinition.



 Comments   
Comment by Eric Hechinger [ 02/Jul/13 ]

Good concept page.
Review info.magnolia.jcr.wrapper.ExtendingNodeWrapper

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