[MGNLUI-6222] DOC: currentItemProvider should not be used in multi fields Created: 21/Sep/20 Updated: 21/Oct/20 Resolved: 14/Oct/20 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 6.2 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Šimon Demočko | Assignee: | Ashraf Khamis |
| 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: Restructure common field properties | ||||||||||||||||||||
| Sprint: | UI FW 13 | ||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||
| Description |
|
We want to avoid currentItemProvider usage with multis (may look for other candidates from code perspective in ConfiguredComplexPropertyDefinition), b/c it leads to issues like The multi nodes could then be resolved by multiple fields that are using currentItemProvider, if they would resolve the same nodes - effectively overwriting each other's contents. Another problem that would result from using currentItemProvider is that if the multi field would be set to resolve non-strictly (strict property set to false, which is the default), the multi would be resolving irrelevant nodes (everything in the parent) which would result in errors. One such place where this could be noted is in |
| Comments |
| Comment by Ashraf Khamis [ 14/Oct/20 ] |
|
Within the scope of this ticket:
More changes will be made as part of a follow-up DOC ticket to document |