[MGNLGQL-25] GraphQL references phase 2 Created: 18/Jun/20 Updated: 04/Mar/21 Resolved: 04/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia GraphQL |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Simon Lutz | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| 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 2 | ||||||||
| Description |
|
This is a follow-up to
User story:
Notes: This is the 'graph' part of graphQL. It is like the 'reference resolving' feature of the Delivery endpoints. Acceptance criteria:
|
| Comments |
| Comment by Christopher Zimmermann [ 04/Mar/21 ] |
|
All features are implemented. Circular reference is not an issue because the developer specifies exactly what they want in the query, it will not overfetch - also not in a loop. (there will be no loop.) |