[MAGNOLIA-6493] Investigate if there are still differences between: Single Area vs. List Area with maxComponents=1 Created: 12/Jan/16 Updated: 16/Oct/21 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | templating, templating components |
| Affects Version/s: | 5.4.3 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Christian Ringele | 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 DoR: |
Empty
|
| Date of First Response: |
| Description |
|
The property on a "list" area "maxComponents" is relative new. Also I have in mind that formerly, when introducing the new templating/rendering with 4.5, the single area created a different content structure (no area node was created). This is not the case anymore since also quite a while. I checked the created content structure and the ui behavior of the two situations. That lead to this ticket: |
| Comments |
| Comment by Richard Gange [ 12/Jan/16 ] |
|
Totally agreed. Every time I explain the areas topic is training I'm scratching my head as to why we need the single type area. Why not just set the maxComponents to 1 on list type? This would reduce the learning curve for new folks. Let's deprecate the single type of area. It's not needed. I also think if we really got creative we could do away with area type all together. |
| Comment by Bradley Andersen [ 10/Aug/16 ] |
|
+1 from me as well. N = 0 is a list I think it is some old remnant whose time has passed. |
| Comment by Richard Gange [ 16/Oct/21 ] |
|
The difference is from the UI perspective on the page. So each configuration produces a different look in the pages app and after second thought it does kind of make sense. This way the user isn't confused by the fact they can only add one component. |