[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: |
| Description |
|
There is a difference in showing components of an area with maxComponents and type:single between Freemarker and Headless. Actual behavior: + SPA: Always shows all components Expected behavior: Note: Before changing the behavior, we should consider its impact to our existing customers |