[MGNLUI-5974] Make content app instances a part of UIComponent hierarchy Created: 18/Jun/20  Updated: 01/Dec/22  Resolved: 01/Dec/22

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

Type: Improvement Priority: Major
Reporter: Aleksandr Pchelintcev Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: FakeMagnoliaUI, new-UI-framework, ui-devx-impr
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-6509 Item added via detail SubApp is not s... Closed
relates to MGNLUI-6214 FMUI - Allow creation of FakeApps tha... Selected
dependency
is depended upon by MGNLUI-5852 Streamline default value configuratio... 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)
Date of First Response:
Story Points: 8
Team: Nucleus

 Description   

Currently the most top-level component inheriting the UIComponent interface are the sub-apps. It seems though that it would make sense to make the apps UI components themselves too.

This would for instance allow us to share datasource definition by the app to all its sub-apps. Also this would generally make the UI component hierarchy more complete.

As part of acceptance criteria, do a fulltext search in UI codebase for "MGNLUI-5974" and apply changes that dependent on this (quick wins, if something is more complicated, file a ticket)



 Comments   
Comment by Dominik Maslanka [ 01/Dec/22 ]

Cannot be prioritized as require lot of resources. Topic will be handled while introducing new UI framework 

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