[MAGNOLIA-3422] Freemarker: expose node depth Created: 29/Nov/10 Updated: 09/Oct/12 Resolved: 02/Dec/10 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core, freemarker |
| Affects Version/s: | 4.3.8 |
| Fix Version/s: | 4.3.9, 4.4.1 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Patch included: |
Yes
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Much like we expose @handle, @uuid, @name, we could expose a @depth and/or @level (our Content API exposes getLevel(), but the JCR equivalent is getDepth()) Maybe this reopens the discussion for exposing all of the above as "regular" properties? Would be fine if we ensure a no-conflict order of resolution (properties, subnodes, then "meta" properties) and keep the @ notation for when we want to enforce the usage of the @meta properties. Are there any other read-only properties / methods not accessible via FreeMarker at the moment ? |
| Comments |
| Comment by Philipp Bärfuss [ 02/Dec/10 ] |
|
Thanks for the patch! |