[MAGNOLIA-2642] aggregation state: use current content property consistently Created: 23/Feb/09  Updated: 23/Jan/13  Resolved: 23/Feb/09

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

Type: Bug Priority: Blocker
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-1479 Refactor ParagraphRenderer/TemplateRe... 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

 Description   

We have cleaned the rendering API but finally we have not change the fact that the so called local content node is not set on the aggregation state.

In magnolia 4.0 we support officially only two global attributes (in the aggregation state)

  • main content (the content we start rendering with, entry point)
  • current content (the currently rendered content, mostly the paragraph node)

all other attributes (used in the tags or Resource class) are deprecated and should not be used.


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