[MGNLUI-4770] Migrate UI registries out of compatibility module (M6.2) Created: 07/Nov/18  Updated: 13/May/22  Resolved: 04/Mar/22

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.0
Fix Version/s: 6.2.18

Type: Improvement Priority: Neutral
Reporter: Hieu Nguyen Duc Assignee: Antonín Juran
Resolution: Fixed Votes: 0
Labels: nucleus
Remaining Estimate: Not Specified
Time Spent: 8m
Original Estimate: Not Specified
Environment:

Magnolia 6.0


Issue Links:
Cloners
is cloned by MGNLUI-7060 Migrate UI registries out of compatib... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Migrate UI FW internals
Sprint: Nucleus 5
Story Points: 2
Team: Nucleus

 Description   
  • Address registry loading order because of validators
  • Reconsider magnolia vs. maven dependencies; build-time vs runtime
  • Let us keep fieldType registry & resolver in compatibility, while moving apps & dialogs to new module
    • keep JCR sources in old module
    • YAML sources to new module

https://git.magnolia-cms.com/projects/PLATFORM/repos/ui/browse/magnolia-ui-framework-compatibility/src/main/java/info/magnolia/ui/framework/UiFrameworkCompatibilityModule.java#112



 Comments   
Comment by Roman Kovařík [ 22/Feb/22 ]

Discovery:

some YAML definitions inherit JCR definitions which are not loaded yet.

We might need to move the startup from the core to jcr module.

Create feature branches for dx-core before integration.

Generated at Mon Feb 12 09:19:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.