Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Merge schemas and resolvers
See original GitHub issueI want to separate my schemas and resolvers to separated files as it’s kinda big right now in one single file.
I found a library called merge-graphql-schemas but I think that it’s redundant with Apollo Server 2 and graphql-tools, the thing is that Apollo Server 2 does already what graphql-yoga does and I don’t need to call makeExecutableSchema in the version 1 as I needed before as it’s now wrapped inside the new ApolloServer (see here so now I’m wondering, how can I use graphql-tools and mergeSchema with Apollo Server 2?
I don’t even know if this approach, I guess called schema stitching is only for remote schemas or it’s suited for local ones as well, like having an schema for user, another one for posts, and so on…
How can I accomplish this?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:9
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@martijnwalraven where are these experimental modules?
I use graphql-import to merge schemas and graphql-merge-resolvers to merge my resolvers. Hope can help you.