[CFGUI-53] Action "Show in Configuration app" doesn't honor extended nodes – app doesn't open correct location Created: 02/Nov/16  Updated: 04/Nov/16

Status: Open
Project: Definitions App
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Philip Mundt Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File the_path_cannot_be_opened.png    
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

When selecting properties in a definition that are actually extended from another node in config workspace, opening the definition in the configuartion app will not work correctly, as the underlying node/property doesn't exist.

Show in Configuration app – JCR + extends

E.g. /.magnolia/admincentral#app:definitions-app:;app~site@subApps/browser/actions/addFolder/icon:treeview
points to config:/modules/site-app/apps/site/subApps/browser/actions/addFolder/icon but all actions are inherited from /modules/ui-admincentral/apps/configuration/subApps/browser via extends.

Show in Resources app – YAML + decorators

Similar, questionable behaviour occurs when selecting a property from a definition coming from yaml that is actually decorated (e.g. /.magnolia/admincentral#app:definitions-app:overview;template~travel-demo~pages/home@areas/main/availableComponents/tourList:treeview:. When hitting Show in Resources app one gets directed to the underlying definition and not the decoration file.

Show in Configuration app – JCR + decorators

Combination of above, similar behaviour.



 Comments   
Comment by Philip Mundt [ 04/Nov/16 ]

As preliminary solution we prevent opening the configuration app when a node doesn't exist in JCR and show a notification to the user:

Generated at Mon Feb 12 00:44:32 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.