[
http://jira.magnolia-cms.com/browse/MAGNOLIA-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Bärfuss updated MAGNOLIA-3422:
--------------------------------------
Fix Version/s: 4.3.9
(was: 4.3.x)
> Freemarker: expose node depth
> -----------------------------
>
> Key: MAGNOLIA-3422
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3422
> Project: Magnolia
> Issue Type: New Feature
> Security Level: Public
> Components: core, freemarker
> Affects Versions: 4.3.8
> Reporter: Grégory Joseph
> Assignee: Philipp Bärfuss
> Priority: Major
> Fix For: 4.3.9, 4.4.1
>
> Attachments: MAGNOLIA-3422.patch
>
>
> 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 ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
