[MGNLUI-6221] Default to jcrChildNodeProvider in JcrMultiFieldDefinition to simplify config and encourage good practice Created: 18/Sep/20 Updated: 30/Oct/20 Resolved: 14/Oct/20 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.4 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Šimon Demočko | Assignee: | Šimon Demočko |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 29m | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||
| Documentation update required: |
Yes
|
||||||||||||||||
| Epic Link: | Simplify YAML configuration | ||||||||||||||||
| Sprint: | UI FW 13 | ||||||||||||||||
| Story Points: | 1 | ||||||||||||||||
| Description |
|
We want to
Thus we're adding default to JcrMultiFieldDefinition This does not pose risk to compatibility because formerly you had to specify the itemProvider. This only takes effect when itemProvider is not specified which before would result in exception. Also, modify the example in https://documentation.magnolia-cms.com/display/DOCS62/Multi+field for JCR Multi Field not to use currentItemProvider there. WIth this change, the whole itemProvider part can (and should) be removed. If we want to how something there still, use jcrChildNodeProvider instead to avoid suggesting CIP - bad practice. |
| Comments |
| Comment by Šimon Demočko [ 18/Sep/20 ] |
|
DOCU update:
|