feat: support multiple graphql endpoints #98
Conversation
This file contains hidden or 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
ypresto
force-pushed
the
feature/multiple-graphql-endpoints
branch
from
be1fb79 to
ecc5617
Compare
|
Hi, I'm really interested by this missing future too which is currently a blocker to continue our tests migration. |
Author
|
@pjean Use below workaround until this PR is merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #63
When the GraphQL endpoint is explicitly specified using
graphql.link('/someGraphqlEndpoint'), the URL is already defined in the handler's endpoint private property. This PR leverages this to support multiple GraphQL endpoints. Therefore, the graphqlUrl option is not necessary when using thegraphql.link(...)form.