[MAGNOLIA-1383] renderers: use them for paragraphs too Created: 16/Feb/07  Updated: 23/Jan/13  Resolved: 18/Apr/07

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 3.0.1
Fix Version/s: 3.1 M1

Type: Improvement Priority: Major
Reporter: Philipp Bärfuss Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-1460 WebContext should provide the HttpSer... Closed
relation
is related to MAGNOLIA-1448 update: lists configuration updates t... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MAGNOLIA-1462 Create a freemarker-based paragraph r... Sub-task Closed Magnolia International  
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)
Date of First Response:

 Description   

A simple change in the inlcude tag would do. The paragraph should get rendered by a plugable renderer as the templates. This would allow other implementations using freemarker for example.



 Comments   
Comment by Magnolia International [ 18/Apr/07 ]

done on trunk.
Introduced ParagraphRenderer and ParagraphRenderingFacade
The Include tag now uses ParagraphRenderingFacade, which in turn delegates to the proper renderer using the node's corresponding paragraph definition.

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