-
New Feature
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Foundation 4, Foundation 5, Foundation 6
-
3
Following type aliases are provided:
- textField, compositeField, linkField, tokenField, twinColSelectField, dateField, checkBoxField, multiField, listSelectField, comboBoxField, codeField, checkBoxGroupField, radioButtonGroupField, richTextField
- jcrStatusColumn, jcrNameColumn, jcrPathColumn, iconColumn, iconAndValueColumn
- commitAction, duplicateNodeAction, addNodeAction, deleteNodesConfirmationAction, closeAction, confirmationAction, openDetailSubappAction
- emailValidator
Acceptance criteria
- duplicates
-
MGNLUI-1209 As a developer I can use symbolic names to define the fieldtype so that I don't need to know the class names
- Closed
- is related to
-
MAGNOLIA-7486 DOC: Field references with $type and 'type resolver'
- Closed
- relates to
-
MAGNOLIA-7469 Annotation processing type resolver implementation
- Closed
-
MGNLUI-4493 Implement sensible replacement to FieldTypeRegistry
- Closed
-
MGNLUI-5172 Add more annotation driven type aliases for UI component parts
- Closed