Details
-
New Feature
-
Resolution: Fixed
-
Major
-
4.3.8
-
None
-
-
Yes
-
Empty show more show less
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 ?
Checklists
Acceptance criteria
Attachments
Issue Links
- is depended upon by
-
MGNLFORUM-120 Support nested messages
-
- Closed
-