[MGNLGQL-2] Provision a GraphQL API based on Content Types Created: 13/May/20  Updated: 29/Jun/20  Resolved: 25/Jun/20

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

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Jaroslav Simak
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 7h
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
Epic Link: GraphQL Phase 1
Sprint: HL & LD 4, HL & LD 5
Story Points: 13

 Description   

User story:

As a developer I want to provision a GraphQL API for the content in magnolia based on content types, so that other systems (including frontends) can use the content.

Notes:

Content types are a way to specify the Magnolia content model.

Acceptance criteria:

  • Developer can provision API using light development
  • It should not require a lot of additional configuration due to reasonable default behaviour.
  • API should return the properties specified in the model.
  • API should respect the relations sepecified in the content types and be able to handle queries that request the referenced content.

Generated at Mon Feb 12 05:51:35 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.