Keep configuration agnostic to datasource
(MGNLUI-7251)
|
|
| Status: | Completed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Roman Kovařík | Assignee: | Adam Siska |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Date of First Response: | |||||||||
| Sprint: | Nucleus 15 | ||||||||
| Team: | |||||||||
| Description |
|
So instead of e.g. $type: jcrTitleColumn I can write just: $type: titleColumn
Use this new config in choosers/app located in UI reactor. This should allow us to move JCR dialogs like chooser to core module and use the same in any datasource with a title column impl. Be aware that for custom config, like custom icons for nodeTypes, the developer would have to use the jcrTitleColumn definition explicitly. |
| Comments |
| Comment by Rabie Hayoun [ 27/Jun/22 ] |
|
A couple notes:
|