Details
-
Task
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
-
Yes
-
UI Framework 16, UI Framework 17
-
5
Description
Current solution involves composite field based solution and requires the presence of redundant static fields for dimensions (width and height) and file name. Those are quirky implementation-wise and also are buggy.
The following improvements should be made to the Upload Field implementation:
- Attach all metadata information that is part of a File to the UploadField (removing the need for redundant static fields).
- Add required property and validation to UploadField
- Enable adding custom factoryClass for the UploadField to maintain flexibility in adding new features to the UploadField (DamUploadField in Assets app).
- Remove redundant static fields from Assets app (and update the app descriptor for the improved UploadField)
- Extract ValueBoundProperty interface from info.magnolia.ui.field.FieldDefinition, which enables adding a Value based property trait to both simple FieldDefinition (which always have a value) or a info.magnolia.ui.editor.ComplexPropertyDefinition (which may or may not have a Value trait).
Checklists
Attachments
Issue Links
- causes
-
EXTDAM-122 Remove custom UploadFieldListenerFactory
-
- Closed
-
- is causing
-
MGNLUI-5886 2 or more UploadFields cannot be used in the same App or Dialog
-
- Closed
-
- is duplicated by
-
MGNLUI-5621 Form does not validate uploadField when it is 'required'
-
- Closed
-
- relates to
-
MGNLDAM-939 JCR DAM has fixed nodetypes for node storing binary data
-
- Closed
-
-
MGNLDAM-822 Asset detail editor - validation for binary file must be on par with M-5-UI
-
- Closed
-
- to be documented by
-
MGNLUI-5680 DOC: UploadViewDefinition
-
- Closed
-