[MAGNOLIA-5419] Single areas should have access to its component in the 'components' model attribute Created: 24/Oct/13  Updated: 19/Dec/16

Status: Open
Project: Magnolia
Component/s: rendering
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Tobias Mattsson Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: rendering
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-5418 Rendering should not fail on single a... Closed
is related to BLOSSOM-148 Area defined as Single Type allows to... 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)

 Description   

It would make sense to expose the single component in the components attribute. List areas have access to it and having it also in the single area would allow them share template scripts.

If there's no component in the area the components attribute should still be there but be an empty list.


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