Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-2546

AggregationState should hold/expose a String templateName instead of an instance of Template

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • Major
    • 4.0
    • None
    • core, templating
    • None

    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.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                gjoseph Magnolia International
                gjoseph Magnolia International
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoR