[MAGNOLIA-3105] manage "children" key in ContentModel to retrieve all children (same type) of current node Created: 04/Mar/10  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: freemarker
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Manuel Molaschi Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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 "?children" builtin calls the ContentUtils.getAllChildren, but if someone needs to have children of the same type without using tag libraries, it would be nice to allow something like "<list page.children as childPage>" that internally calls content.getChildren().



 Comments   
Comment by Magnolia International [ 08/Mar/10 ]

Agreed - but we need to weight the impacts of such a change; in most cases, you indeed want to see only the "same type children" (when building navigation menus or rendering paragraphs), but there are cases where you need to get children of a different type (listing documents off of a mgnl:folder from dms)

Whichever option we choose, we'll probably have to expose the counterpart as a utility method, for instance in MagnoliaTemplatingUtilities - I don't think the ?children built-in of FreeMarker accepts a parameter.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:43:14 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.