[MGNLUI-5464] DOC: Multivalue field - 6 UI Created: 31/Oct/19 Updated: 30/Jan/20 Resolved: 30/Jan/20 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 6.2 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Ashraf Khamis | Assignee: | Martin Drápela |
| Resolution: | Done | Votes: | 0 |
| Labels: | fields, new-UI-framework, new-form | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | DOC: Documentation for Magnolia 6.2 | ||||||||
| Sprint: | UI Framework & 6.2 Ramp up 15 | ||||||||
| Story Points: | 1 | ||||||||
| Description |
|
Merge these new pages into one new MultiField page:
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. |