[MGNLUI-2547] Initialize controlMigrationMap on execution call of the dialogMigrationTask Created: 07/Jan/14  Updated: 31/Jan/14  Resolved: 07/Jan/14

Status: Closed
Project: Magnolia UI
Component/s: dialogs
Affects Version/s: 5.2.1
Fix Version/s: 5.2.2

Type: Bug Priority: Neutral
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 MGNLFORM-221 Migrator has to access the ControlMig... Closed
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

 Description   

Currently, the controlMigrationMap is initialized based on controlMigratorsRegistry elements during class construction. This means that all migrator register later by others version handler are not visible to the current dialogMigrationTask.
This is wrong.
The controlMigrationMap has to be initialized based on controlMigratorsRegistry once the execute() method is called.


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