[BLOSSOM-147] Support for specifying maximum components in an area Created: 17/Oct/13  Updated: 06/Dec/14  Resolved: 21/Feb/14

Status: Closed
Project: Blossom
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0.4, 3.0.1

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

Issue Links:
relation
is related to MAGNOLIA-4901 Add possibility to set maximum number... 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)
Date of First Response:

 Description   

The Area annotation should allow specifying the maximum number of components that can go in an area. The default should be no limit.

Mentioned in http://forum.magnolia-cms.com/forum/thread.html?threadId=996f7297-07ae-47c7-902e-c64d9d034ccb and http://forum.magnolia-cms.com/forum/thread.html?threadId=5060d187-1d06-4725-b073-f3b327a701b4

The current solution would be to use a custom DialogDescriptionBuilder to set the maximum number. Either by checking for an annotation of your own that allows for specifying the limit or by hardcoding checks for specific classes and setting the limit based on that.

Add this to use a custom TemplateDefinitionBuilder:

<bean class="info.magnolia.module.blossom.template.TemplateExporter">
  <property name="templateDefinitionBuilder">
    <bean class="my.package.MyTemplateDefinitionBuilder" />
  </property>
</bean>


 Comments   
Comment by Jan Haderka [ 06/Dec/14 ]

Bulk close of old resolved tickets.

Generated at Sun Feb 11 23:30:36 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.