Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-2500

Create a Dialog migration task that uses a Control migrators registry.

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major Major
    • 5.2.1
    • 5.2
    • dialogs, framework
    • None

      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

        Acceptance criteria

              ehechinger Eric Hechinger
              ehechinger Eric Hechinger
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Task DoR