[MAGNOLIA-5260] Template variations need to be resolved prior to rendering in order to override renderType Created: 26/Aug/13  Updated: 20/Sep/13  Resolved: 13/Sep/13

Status: Closed
Project: Magnolia
Component/s: rendering, templating
Affects Version/s: 4.5.10, 5.0.3
Fix Version/s: 4.5.12, 5.0.5, 5.1

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

Issue Links:
dependency
relation
is related to MAGNOLIA-5233 Template variation always inherits th... 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
Date of First Response:
Sprint: 5.1 - RC1

 Description   

Area variation is currently resolved in DefaultRenderingEngine.render().
Variation needs to be set for every subarea again, see problem with defining of renderType - SUPPORT-2634 for details.
Consider resolving of variation in AreaElement already or find another way to inherit renderType of parent.



 Comments   
Comment by Jan Haderka [ 10/Sep/13 ]

Please make it so that deprecated constructor calls the new one rather then super to make it obvious they do the same thing.

Comment by Jan Haderka [ 10/Sep/13 ]

Also I think we should not be introducing new constructor in 4.5 but only in 5.x since new constructor requires all extending classes to provide this constructor as well.

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