[MAGNOLIA-9157] SPA should respect 'maxComponents' and 'type:single' when an area has more components Created: 24/Oct/23  Updated: 14/Nov/23

Status: Accepted
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Anh Vu Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Epic Link: Headless Backlog
Team: DeveloperX

 Description   

There is a difference in showing components of an area with maxComponents and type:single between Freemarker and Headless

Actual behavior:
+ Freemarker: Shows components based on maxComponents or type:single. 
  - For type:single, shows only the first component if there are more than one component
  - For maxComponents = N, shows the first N components if more than N components exist

+ SPA: Always shows all components

Expected behavior:
SPA shoud have the same behavior as Freemaker.

Note: Before changing the behavior, we should consider its impact to our existing customers


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