[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Bracher updated MAGNOLIA-2546:
--------------------------------------
Fix Version/s: 4.0 RC1
(was: 4.0)
> AggregationState should hold/expose a String templateName instead of an
> instance of Template
> --------------------------------------------------------------------------------------------
>
> Key: MAGNOLIA-2546
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2546
> Project: Magnolia
> Issue Type: Task
> Components: core, templating
> Reporter: Gregory Joseph
> Assignee: Gregory Joseph
> Fix For: 4.0 RC1
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
