[MGNLUI-5394] Migrate app launcher layout config into a non-deprecated module Created: 24/Sep/19 Updated: 23/Apr/21 Resolved: 06/Apr/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.8 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | VN-Testing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 6h 32m | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||||||||||||||
| Documentation update required: |
Yes
|
||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||
| Epic Link: | Migrate UI FW internals | ||||||||||||||||||||||||||||||||
| Sprint: | UI Framework 7, UI FW 25 | ||||||||||||||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||||||||||||||
| Description |
|
Currently the apps, old and new have to add app launcher registration bootstrap files that point to the now deprecated ui-admincentral module. We need to let at least the updated apps to avoid doing that and register themselves through updated admincentral (preferrably via YAML). TODO:
OUTCOME Let's keep everything as is for 6.2. This will give us have time to decide if we’ll go with JCR or YAML for applauncher ordering support
|
| Comments |
| Comment by Roman Kovařík [ 30/Sep/19 ] |
|
Yes that was the idea, as we don't have time to migrate all modules plus we should support old customers modules as well. |
| Comment by Roman Kovařík [ 25/Mar/21 ] |
|
For documentation: You can now configure appLauncher via decoration: magnolia-personalization-personas-app/src/main/resources/personalization-personas-app/decorations/admincentral/config.yaml
appLauncherLayout:
hiddenApps:
- notifications
groups:
- name: target
apps:
- name: personas-app
You can specify the order in a group by providing complete list of apps with !override
appLauncherLayout:
groups:
- name: target
apps: !override
- name: preview-app
- name: personas-app
- name: segmentation-app
You can still use the old applauncher config in JCR. Be aware that the order of apps is merged from new and old config (first the app from YAML, next the apps from JCR). |
| Comment by Roman Kovařík [ 25/Mar/21 ] |
|
PoC: https://git.magnolia-cms.com/projects/PLATFORM/repos/ui/pull-requests/1750/overview |
| Comment by Roman Kovařík [ 06/Apr/21 ] |
|
Reopened due to migration diff https://jenkins.magnolia-cms.com/job/internal/job/migration-tests/job/6.2-to-6.2.x/260/Diff_20Report/ |
| Comment by Roman Kovařík [ 23/Apr/21 ] |
|
For release notes: The pages app ( appLauncherLayout: groups: edit: #remove from default location apps: pages-app: enabled: false manage: #you can still use the old JCR config instead of this part apps: pages-app: enabled: true |