Skip to content

Parsing Schema vs. Using Structs to define schema #506

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Chandlerblaid opened this issue Aug 28, 2019 · 1 comment
Open

Parsing Schema vs. Using Structs to define schema #506

Chandlerblaid opened this issue Aug 28, 2019 · 1 comment

Comments

@Chandlerblaid
Copy link

Let's say that I have an existing schema:

const Schema = ' type Gamer { id: String! } type Query { gamers: [Gamer] }'

If I want to use graphql-go to handle this schema, would it be best (in terms of efficiency and extensibility) to use graphql.MustParseSchema(Schema, &Resolver{}) or to recreate the schema using the graphql-go structs to create new graphql objects?

@asaf
Copy link

asaf commented Sep 3, 2019

see #119

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants