[MGNLGQL-17] Provision a GraphQL API for Stories app content Created: 13/May/20  Updated: 17/Jun/20

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

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Unresolved 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 2

 Description   

User story:

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

Notes:

We do not yet support generating a stories app based on a content type. A possible solution to this special case would be to add content type support for Stories apps. This would probably also require defining content types for the available blocks.

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 stories app content model.
  • API should respect the relations sepecified in the stories app and be able to handle queries that request the referenced content.


 Comments   
Comment by Simon Lutz [ 17/Jun/20 ]
  • As pages, stories are very dynamic and use three dots notation to return blocks
Generated at Mon Feb 12 05:51:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.