Details
-
Task
-
Resolution: Done
-
Neutral
-
None
-
6.2
-
None
-
-
Empty show more show less
-
Empty show more show less
-
UI Framework & 6.2 Ramp up 15
-
1
Description
Merge these new pages into one new MultiField page:
- https://documentation.magnolia-cms.com/display/DOCS62/JSON+multi+field
- https://documentation.magnolia-cms.com/display/DOCS62/JCR+multi+field
Old description:
Create a new page for multivalue field in Magnolia 6 UI. The existing page for Magnolia 5 UI can serve as an inspiration.
Sasha (Slack, Oct 31st, 2019)
It is not as simple as 1 to 1 mapping here. The complex fields are no longer treated as 'fields' per se. In the form implementation, they are treated as complex properties or subeditors (parts of the form that in turn may have child fields). For example, there is a definition for composite field in the Magnolia 6 UI framework, but no implementation since it just reuses FormView with a different layout.
For multivalue fields, info.magnolia.ui.framework.databinding.MultiFormView plays the role of multifield substitution. We may develop eventually some kind of ArrayField for the multifields that consist of trivial entries (meaning that MultiformView manages complex cases where you may have a set of subforms like RSS entries in the Feeds app, while ArrayField might have a simpler implementation but would only manage a list of text or other fields).
Checklists
Attachments
Issue Links
- relates to
-
MGNLRESTUI-12 DOC: REST entities support complex fields
-
- Closed
-
- mentioned in
-
Page Loading...