[MGNLUI-2500] Create a Dialog migration task that uses a Control migrators registry. Created: 09/Dec/13 Updated: 16/Dec/13 Resolved: 13/Dec/13 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | dialogs, framework |
| Affects Version/s: | 5.2 |
| Fix Version/s: | 5.2.1 |
| Type: | Task | Priority: | Major |
| Reporter: | Eric Hechinger | Assignee: | Eric Hechinger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||||||||||
| Description |
|
Currently, the control migrators registered in a dialog migration task are inherited by class hierarchy. A custom module may want to uses the migrators defined in Dam, but also the Category and Data one. This is currently not possible but necessary. The solution is to use a registry of migrators defined at the module level, and to define a new DialogMigration task that uses those registry to build the available migrators list. Task:
|