[MGNLUI-4624] App launcher should always reflect the latest configuration Created: 11/Sep/18  Updated: 14/Nov/23

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

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File app-no-actions.png    
Issue Links:
Relates
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)
Release notes required:
Yes
Epic Link: Content Types phase 2

 Description   

As a developer, I want the app launcher to always reflect the latest configuration, so that I can work efficiently and without hassle.

Acceptance criteria:

  • Ideally as soon as the configuration is changed, then the app launcher is refreshed.
  • If the above is not possible, then when I do a browser refresh, the app launcher should reflect the actual configuration, and the app must work properly.

The use case is that as a developer I am either creating a new app (via contenttypes) and it should show up beause the "defaultGroup" property is enabled, or I am manually working on the app launcher configuration - and of course I need to see if I have done it right, or how it is going to look. Currently to do this I need to log out and log in again, which is time-consuming, annoying, and unexpected.

Notes:

My idea is to refresh it when a user does a browser refresh, but if there is some alternative better method to refresh it automatically with no user action - then do that.



 Comments   
Comment by Christopher Zimmermann [ 11/Sep/18 ]

If a push mechanism could cause the app layout to be instantly automatically refreshed when the configuration changes, that would be amazing.

Comment by Christopher Zimmermann [ 14/Nov/23 ]

I just tested this on 6.2.38. Its behaving slightly better - but there are still problems.

When I add a content type to light module (I used "mgnl" CLI). The system registers the change (visible in logs) but I do not see the app in the app launcher, even if I open and close an app. If i take an action - then I see the blue "Workspace Initialized" message. But not the new app. 

If i refresh the browser - then I finally see the app in the app launcher. But when I open that app - there are no actions available. So I cannot create content.

If i log out and in again - then I see the app and it has actions and works.

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