[MGNLUI-675] Simplify defining a main subapp Created: 19/Feb/13  Updated: 28/Feb/13  Resolved: 27/Feb/13

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

Type: Improvement Priority: Major
Reporter: Daniel Lipp Assignee: Daniel Lipp
Resolution: Fixed Votes: 0
Labels: app-api
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLUI-740 Default subApp sometimes returns wron... Closed
is causing MGNLWORKFLOW-34 Adapt to changes from simplification ... Closed
is causing MGNLDAM-148 Adapt to changes from simplification ... Closed
relation
is related to MGNLUI-678 Streamline Security App 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)

 Description   

Right now all subapps are equal (codewise) - any subapp (even several) could be configured to be the "default". The default app is opened first and cannot be closed.

We should simplify by simple choosing the first subapp as being the default. Having a dedicated property for the main and a collection for the other subapp seams to be unecessarily complicated.


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