As a system administrator, I can migrate my custom types from the data module to content apps
(MGNLDATA-201)
|
|
| Status: | Closed |
| Project: | Magnolia Data Module (closed) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.2 |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Mikaël Geljić | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | migration | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Sprint: | 5.2-rc2 |
| Description |
|
For editing multiple types, we use a single action that triggers a location change based on item type. We do it in the same flavor as the new ResourceEditItemAction. We assume we will have various detail subapps named after their former type name in 4.5. We don't add the create actions in this step, just editing |
| Comments |
| Comment by Mikaël Geljić [ 31/Oct/13 ] |
|
We should not both log and throw exceptions, choose either option that makes more sense this is in CreateDataAppTask#doExecute and #createApp |