[MAGNOLIA-2546] AggregationState should hold/expose a String templateName instead of an instance of Template Created: 12/Jan/09  Updated: 23/Jan/13  Resolved: 12/Jan/09

Status: Closed
Project: Magnolia
Component/s: core, templating
Affects Version/s: None
Fix Version/s: 4.0

Type: Task Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MAGNOLIA-2370 Move Template/Paragraph related code ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

There's no real reason for this, except abstraction - we're moving all Template related code to the templating module. In fact, one might argue that there's no reason for the AggregationState to even hold the template node. If a custom module would want to change the template in use, it might as well change the RenderingFilter instead of modifying the data in AggregationState.


Generated at Mon Feb 12 03:37:46 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.