[MGNLUI-7060] Migrate UI registries out of compatibility module on cloud branch Created: 10/Mar/22  Updated: 12/Apr/22  Resolved: 28/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: Roman Kovařík
Resolution: Done Votes: 0
Labels: VN-Testing, nucleus
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia 6.0


Issue Links:
Cloners
clones MGNLUI-4770 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 6, Nucleus 7
Story Points: 5
Team: Nucleus

 Description   

We to address below point on cloud branch (feature/magnoliaUIVersion.6-3-SNAPSHOT)

  • 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?at=refs%2Fheads%2Ffeature%2FmagnoliaUIVersion-6.3-cloud-SNAPSHOT



 Comments   
Comment by Rabie Hayoun [ 10/Mar/22 ]

Discovery Completed

we need to applies the same refactoring to the cloud branch. Rebasing might cause issue, so ultimately we should just move the code from compatibility to the right file.

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