[MGNLGQL-37] Add support for defining enums and scalars via yaml Created: 03/Jul/20  Updated: 07/Aug/20  Resolved: 07/Aug/20

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

Type: Improvement Priority: Neutral
Reporter: Jaroslav Simak Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLGQL-6 GraphQL simple filters Closed
is depended upon by MGNLGQL-23 GraphQL filter on metadata Closed
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)
Epic Link: GraphQL Phase 1

 Description   

So far, our implementation only allows to specify Object types to be configured in the GraphQLDefinition.

This ticker proposes to extend current functionality to also add Enums and Scalars.

All three types (Objects, Enums and Scalars) will have a common ancestor and will be defined in the GraphQLDefinitions.


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