[MGNLUI-5552] Clarify the semantics of the viewType property of OpenDetailSubappActionDefinition Created: 10/Dec/19 Updated: 11/Dec/19 Resolved: 11/Dec/19 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | framework |
| Affects Version/s: | None |
| Fix Version/s: | 6.2 |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Michael Duerig | Assignee: | Michael Duerig |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Epic Link: | UI framework: forms, dialogs, content editing |
| Sprint: | UI Framework 12 |
| Story Points: | 1 |
| Description |
|
i.m.ui.contentapp.action.OpenDetailSubappActionDefinition#viewType is an opaque string. It's semantics and default value is not evident. According to i.m.ui.contentapp.ResolveJcrNodeFromLocationContext#resolveNode permissible values are add, edit, view, version and the empty string. The latter is the default and results in the fields in the detail subApp not being populated. As discussed on Slack this area might undergo further changes in the future. In the meanwhile I suggest to add a doc comment for the current behaviour and change the default value to view. |