[MAGNOLIA-6168] FragmentDefinition on RenderableDefinition should not have a default Created: 15/Apr/15  Updated: 01/Jul/15  Resolved: 15/Apr/15

Status: Closed
Project: Magnolia
Component/s: rendering
Affects Version/s: 5.4
Fix Version/s: 5.4

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MAGNOLIA-6039 Implement FragmentDefinition on Rende... Closed
is causing MGNLADVCACHE-49 FragmentInjectionListener should chec... Closed
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
Epic Link: DPC

 Description   

With MAGNOLIA-6039, we introduced FragmentDefinition, and gave it a default value in ConfiguredRenderableDefinition. This causes incorrect merging with site definitions:

 private FragmentDefinition fragmentDefinition = new StaticFragmentDefinition();

The StaticFragmentDefinition class can be probably dropped altogether.


Generated at Mon Feb 12 04:11:56 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.