aerogear/create-graphql

Read existing 'schema.json' to serve querys/mutations

Open

#12 opened on Dec 6, 2016

View on GitHub
 (4 comments) (2 reactions) (0 assignees)JavaScript (440 stars) (51 forks)batch import
enhancementhelp wanted

Description

If we could read an existing schema.json file, for creating the types, queries and mutations allowed by the server, it would be great for frontend development...

Another improvement would be generating "Loren Ipsun"-style data for each type.

This is specially useful for other backend languages/frameworks (Flask, Django, Rails, etc) that generates schema.json file.

Contributor guide

Tech stack
javascriptnodejsgraphql
Domain
backendcliapi
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaScriptGraphQL basicsNode.js filesystem
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Investigate how create graphql currently generates GraphQL types. Look for existing schema.json handling in the codebase, likely in src/. Check comment threads for additional context on desired data generation (e.g., faker library). Consider adding a command line flag to specify the schema file path. The issue suggests generating Lorem Ipsum style data per type; research libraries like @faker js/faker for random data generation.