[MGNLREST-203] Delivery API - Filter nodes based on child node properties Created: 28/May/19  Updated: 04/Apr/22

Status: Accepted
Project: Magnolia REST Framework
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Loukas Andreadelis Assignee: Unassigned
Resolution: Unresolved Votes: 2
Labels: collector-0cf1239d
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Issue Links:
Relates
relates to MGNLREST-321 Delivery API - Filter nodes by by cat... Accepted
causality
dependency
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:
Epic Link: Headless Backlog

 Description   

User Story:

As a developer, I want to filter on properties of subnodes as well as top level nodes, so that I can get the nodes that I am looking for.

Notes:

Currently, it is possible to request nodes using filtering on root node properties. However, it is not possible to filter out nodes based on a list of properties (that is, child node properties). This is a common use case. For example, a node might have a child node with a list of locations - a client should be able to filter for one of those locations.

More detailed description can be found at this ticket:

https://jira.magnolia-cms.com/browse/SUPPORT-9985

 



 Comments   
Comment by Christopher Zimmermann [ 28/May/19 ]

Would have changed Reporter to myself, but apparanetly that's not possible now.

Comment by Henry Steinberg [ 26/Jul/21 ]

Any more info available on this? This feature would be very welcome.

Comment by Christopher Zimmermann [ 26/Jul/21 ]

No concrete plans at the moment steinberghenry. Care to share any details about your use case and about the pain of not having this feature?

Comment by Henry Steinberg [ 02/Aug/21 ]

Apologies for the delay in replying, we've created a separate ticket here

Generated at Mon Feb 12 06:57:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.