[MGNLUI-5325] Support defaultValue in fields of new ui framework Created: 14/Aug/19 Updated: 07/May/21 Resolved: 14/Aug/20 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 6.2, 6.2.1 |
| Fix Version/s: | 6.2.3 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Federico Grilli | Assignee: | Aleksandr Pchelintcev |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | 62-UI-1, 622, defaultValue | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 0.3d | ||
| 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)
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | UI framework: configuration | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Maintenance 16, Maintenance 17, UI FW 7, UI FW 8 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Timebox: Find out via support tickets and other investigation which types of default values are problematic other than the example given in the last paragraph here. 5 SP In M5 fields have the ability to support default values (optional property defaultValue), in order to present users with some predefined choices. It was assumed that the value was a String. This property is still in the new field definition and now accepts a generic argument. Back in the day, a possible implementation was attempted, e.g. in the case of JCR, by specifying a node name (the configuration is commented out and still visible at contacts-v8.yaml). This no longer works as ItemToLinkConverter at JcrSelectFieldSupport tries to retrieve the model (a JCR Node) by uuid. However, when a defaultValue is provided as a node name the converter throws an exception (I assume that using uuid as default values would be most inconvenient for users). Dev notes:
|
| Comments |
| Comment by Viet Nguyen [ 23/Jun/20 ] |
|
Question from mboehm:
|
| Comment by Aleksandr Pchelintcev [ 22/Jul/20 ] |
|
jayala can you pls double-check whether you still can reproduce the example you attached - worked correctly for me with the latest 6.2.2 |
| Comment by Roman Kovařík [ 18/Aug/20 ] |
|
The default values are now supported in new framework.
|