Feature: Export generateProxyingResolver, handleResult for v5.0.0 #1569
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…for users to be able to generate their own proxying resolvers for a schema instead of having to attach it to a schema directly.
marcammann
changed the title
|
So we can close this in favor of #1570 ? |
|
Do we still need this PR? @marcammann |
|
I think we can close this one. I spent a late night migrating our stuff to graphql-tools 6.0.0 — had to make that executor switch at some point :) Thank you! I'll re-open if this migration goes sideways by the end of the day. |
|
Please feel free to ask any questions related to your migration process. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As mentioned in #1568, this PR adds exports for
handleResultandcreateProxyingResolverto quickly create a ResolverMap without having to create a schema.This PR is supposed to patch v5.0.0, so no rebasing against
master. I can make another one for v6.0.0 if it's still present there.