[MGNLUI-222] ItemSubApp: creating a new item and passing it to the subapp Created: 26/Nov/12 Updated: 13/Mar/13 Resolved: 13/Mar/13 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | app framework, framework |
| Affects Version/s: | 5.0 |
| Fix Version/s: | 5.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Espen Jervidalo | Assignee: | Espen Jervidalo |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | apiteam, framework | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| 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: | |||||||||
| Description |
|
From info.magnolia.ui.admincentral.form.action.CreateItemAction The ItemSubApp only gets a location containing nodePath and View Type. |
| Comments |
| Comment by Philipp Bärfuss [ 29/Nov/12 ] |
|
I don't think we should create temporary nodes. That is what we wanted to avoid. If a user uses the 'new' action and then cancel the creation, nothing should have happened to the workspace. |
| Comment by Daniel Lipp [ 29/Nov/12 ] |
|
Seems to be worth investigating whether JcrItemAdapters (JcrNewNodeAdapter) cannot be used. Sound like a similar use case. |
| Comment by Daniel Lipp [ 04/Dec/12 ] |
|
Lowered the prio and moved to next sprint. Current solution is not ideal but working. |