[MGNLSITE-68] Analyse: Template definition as a merge of prototype and single template definition Created: 09/Aug/16 Updated: 31/May/21 Resolved: 31/May/21 |
|
| Status: | Closed |
| Project: | Magnolia Site Module |
| Component/s: | None |
| Affects Version/s: | 1.0.8 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Mercedes Iruela | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoR: |
Empty
|
||||
| Date of First Response: | |||||
| Description |
|
Nowadays, prototype and base template definition is merged only on rendering, we have received on support a suggestion that says the 'A TemplateDefinition by design should always be the merged result of prototype and single definition' It is something new and might be necessary to analyse the side effects of this change and if it is really worthy. |
| Comments |
| Comment by Jan Haderka [ 31/May/21 ] |
|
Template definition object is designed to aid template rendering. As such the definitions are and will be merged fully only at the time of rendering. Please reopen with rationale and additional use cases to evaluate if there is valid need to use TDs outside of rendering and force full resolution and merge upon every change to TDs or their parent definitions. |