[MAGNOLIA-8084] Decoration origin discrepancy in console and in definitions app Created: 06/May/21  Updated: 06/May/21

Status: Open
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Martin Drápela Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2021-05-06-08-11-46-329.png    
Issue Links:
Problem/Incident
is caused by MGNLSITE-102 DOC: Yaml-based site definition howto... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Example:

When I create a new site by decoration from a light module (file system), the console says:

2021-05-05 15:29:24,980 INFO fig.source.yaml.decoration.YamlDefinitionDecorator: Applied YAML file based decorator from [/hello-magnolia/decorations/multisite/config.yaml] to definition provider [[module] definition [multisite] with reference id: [multisite] from module [multisite] at [/modules/multisite/config]]

But the definitions app shows JCR as the origin of that configuration:

Seen in:

Version number : 6.2.8 Core version : 6.2.8 Build : 26. April 2021 (rev. 1612902596be8952ce23733cbcd705186f9c3fa3 of UNKNOWN) Edition : Magnolia DX Core


 Comments   
Comment by Roman Kovařík [ 06/May/21 ]

Developer notes:

  • As the origin is known only for definitions, decorations are not relevant
  • Decorations come nowadays only from YAML, but we don't know which part of the definition is the decorated one anyway
  • Due to the above, to prevent confusion, the definition app could just not show the origin info for definition properties (in this case, move ticket to the definition app project).
Generated at Mon Feb 12 04:29:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.