Skip to content
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

Question: Can resolvers be modularised & merged in the load process #11

Open
serle opened this issue May 3, 2017 · 3 comments
Open

Comments

@serle
Copy link

serle commented May 3, 2017

I was considering using the same approach until I came across the talk. Can the resolver file for each .graphql file sit alongside its corresponding schema and be merged into an executable schema by your loaded? I would also like some form of co-location of the two halves of the picture

@Panoplos
Copy link

Upvote on this request. Seems like this tool is nothing more than a toy if you cannot load co-located resolvers for queries, mutations and custom types.

@jakelacey2012
Copy link

I did something very similar to this, checkout https://github.com/RedLeap/GraphQL

@Panoplos
Copy link

Panoplos commented Jul 4, 2017

Thing is, graphql-tools seems to be moving in this direction... The only real difference is you have to manually load your gql files into memory, then feed them to makeExecutableSchema.

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

3 participants