[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:
dependency
depends upon MAGNOLIA-5543 Use Components to create new instance... Closed
is depended upon by MGNLCAT-120 Register ControlMigrators in the Cate... Closed
is depended upon by MGNLDAM-360 Register ControlMigrators in the DAM ... Closed
is depended upon by MGNLDATA-233 Register ControlMigrators in the Data... Closed
is depended upon by MGNLFORM-216 Register ControlMigrators in the Form... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

Currently, the control migrators registered in a dialog migration task are inherited by class hierarchy.
For example, DialogMigrationTask define a bunch of migrators, and his sub class DamDialogmigrationTask add migrators.

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:

  • Create a new ControlMigratorsRegistry.
    • Singleton filled by the modules version handlers that defines custom controls and migrators
  • Define a new DialogMigratortask that uses this registry (DialogMigrationRegisteryTask)
  • Adapt the module version handlers that defines specific ControlMigrators
  • Adapt the existing DialogMigrationTask in order to be backward compatible

Generated at Mon Feb 12 08:57:15 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.