-
Improvement
-
Resolution: Done
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Yes
-
Basel 145, Basel 147
-
8
User story:
As a developer, I have two fields: textField and text. They are both bound to the same field definition class. Which one to pick and why? (If the lookup is still happening by definition class.)
Investigate and prototype how (and if) the field selection process can work in the pressence of:
- Two fieldtype definitions have the same definition class.
- One of them is deprecated.
- The deprecated one is decorated.
In general the non-deprecated fieldType should be chosen.
However if the deprecated one is also decorated - then that one should be chosen.
Context:
As part of the effort to allow fields to be referenced by name in a form, we want to rename some fields to make the naming consistant. To do this we create new fieldTypes with the new name, and deprecate the existing field types.
See: "Disambiguating duplicate field-types" here: https://wiki.magnolia-cms.com/display/ARCHI/2018-04-10+Reference+fields+by+name%2C+rename+field+types
Proposed solution:
info.magnolia.ui.form.fieldtype.registry.FieldTypeDefinitionRegistry#getByDefinition will be adjusted to behave in favour of non-deprecated or decorated types when queried.
- is depended upon by
-
MGNLUI-3882 Reference fields by name as well as by fully qualified classname
- Closed
- relates to
-
MAGNOLIA-7318 DialogDefinitionValidator should handle deprecation cases correctly
- Accepted
- mentioned in
-
Page Loading...