How can we handle separate files for resolvers and...
# orm-helpa
Anders
10/20/2018, 8:51 AMHow can we handle separate files for resolvers and schema? I would like to have one file per concern. Eg User.graphql and UserResolver.js
Then
Comment.graphql and CommentResolver.js
k
kitze
10/20/2018, 10:14 AMkitze
10/20/2018, 10:14 AMJust import all the individual schema.graphql types on the top of the main schema.graphql
a
Anders
10/20/2018, 10:33 AMSorry I was unclear, Im talking about graphql-yoga and not prisma. Does that work there? Package? Can mutations also reside in the import?
k
kitze
10/20/2018, 10:52 AMNo idea
kitze
10/20/2018, 10:52 AMI would love to separate the mutations on line 12-13 and 16-17 to their respective files, but I'm not sure if it's possible
a
Anders
10/20/2018, 11:12 AMI guess you could use extend?
https://github.com/apollographql/graphql-tools/issues/242
Anders
10/20/2018, 11:36 AMI’m going to try this one out. Seems all that we want....
https://www.npmjs.com/package/merge-graphql-schemas
Any thoughts?
l
lawjolla
10/20/2018, 10:39 PMI'm using and it works well. Just lookout for this gotcha https://github.com/okgrow/merge-graphql-schemas/issues/153
3 Views