Hack to get GraphQL 14 to work #15
Merged
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
|
@acarl005 Is this repo dead? |
|
@flippidippi @GlennMatthys Now that extensions have been added to https://github.com/graphql/graphql-js/releases/tag/v14.5.0 |
|
I haven't done any research into how to get it working with the new graphql |
|
@flippidippi thanks for the response and PR—released in |
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.
Using the hack seen here join-monster/join-monster#352 (comment), this allows join-monster-graphql-tools-adapter to work with GraphQL 14 until graphql-js adds something like extensions described here graphql/graphql-js#1527.
This could, for the time being, fix #12