Details
-
Bug
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
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.