[MGNLSTK-712] enable the "parameters"-feature also for the Area class. Created: 23/Nov/10 Updated: 05/Jun/13 Resolved: 05/Jun/13 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | None |
| Affects Version/s: | 1.3.4 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor |
| Reporter: | Stefan Baur | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | area, parameters | ||
| Remaining Estimate: | 1d | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | 1d | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
For templates and paragraphs, we have the feature of adding parameters and accessing those values just by ${def.key} (instead of def.parameters.key). It would be very nice, if this was possible also for Areas (for example: def.footer.parameters.key) |
| Comments |
| Comment by Magnolia International [ 17/Dec/10 ] |
|
Hi Stefan, Makes sense. But currently, the Area class does not have a parameters map. So there'd be two things needed: 1) adding this Map 2) adding the freemarker "shortcut", similar to info.magnolia.module.templating.freemarker.RenderableDefinitionModel What is your use case ? Maybe you could achieve something similar by nesting paragraphs ? |
| Comment by Stefan Baur [ 17/Dec/10 ] |
|
Hi Greg I have no special case. i came across several situations in a project, where this feature would have been an easy solution. And i thought, adding this map would be a very small change without further implications... So I just opened this ticket to ask |
| Comment by Philipp Bärfuss [ 21/Dec/10 ] |
|
I agree that the areas are becoming more and more a base component and should have similar properties as the paragraphs and templates. We are moving in that direction for Magnolia 5.0. |
| Comment by Stefan Baur [ 18/Jan/13 ] |
|
Going through my reported tickets... Nicely implemented with STK 2.x! Can be closed... |