-
Story
-
Resolution: Done
-
Neutral
-
5.4.6
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Yes
-
Basel 79, Basel 147
-
13
Currently in a dialog definition, to specify the type of field you must supply a fully qualified class name of the field, for example:
info.magnolia.ui.form.field.definition.TextFieldDefinition
For legibility, ease of development, and to make fields easier to remember, a developer should be able to use a short name instead of needing to specify the class name. (But the fully qualified class name may still be used.) In this case:
text
Still to decide is which field should be used to supply this field name, maybe the same field "class" or a new field "fieldType".
A developer should not have to specify a different dialog class for this functionality - it should work with the current default dialog.
Validation: https://wiki.magnolia-cms.com/display/PMTEAM/Simplified+Dialogs+LDV
- depends upon
-
MAGNOLIA-6901 Generalise bean type resolution strategy in to-bean transformers
- Closed
-
MGNLUI-4377 Report references to deprecated fieldType definitions for app registry
- Closed
-
MGNLUI-4380 Report references to deprecated fieldType definitions for dialog registry
- Closed
-
MGNLUI-4427 Disambiguating duplicate field-types
- Closed
- is depended upon by
-
MAGNOLIA-6664 Inheritance of registry definitions from YAML
- Closed
-
MGNLUI-4496 Infer field definition type from 'type' property
- Closed
- relates to
-
MGNLUI-4135 Enable reference-fields-by-name
- Closed
-
MAGNOLIA-6928 TypeResolvers do not report any problems making it hard to identify issues with definitions
- Accepted
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...