[MGNLGQL-16] GraphQL delivers heirarchical content Created: 13/May/20 Updated: 29/Jun/20 Resolved: 17/Jun/20 |
|
| Status: | Closed |
| Project: | Magnolia GraphQL |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | 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)
|
| Documentation update required: |
Yes
|
| Date of First Response: | |
| Epic Link: | GraphQL Phase 1 |
| Description |
|
User story:
Notes: In the delivery endpoint, I have two ways to query - one is a search that ignores heirarchy, one is getting a node and its children. Acceptance criteria:
|
| Comments |
| Comment by Simon Lutz [ 17/Jun/20 ] |
|
Not possible in GraphQL world - jsimak please add your comments. |
| Comment by Christopher Zimmermann [ 29/Jun/20 ] |
|
Created https://jira.magnolia-cms.com/browse/MGNLGQL-34 in order to cover some of the use cases that this would have provided. |