Revert "Pin graphql-core to <3.0.0" #49
Merged
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.
Upstream pinned
gql
to graphql-core<2.0 so I am suggesting we revert #29 which forced us to use graphql-core<3. Users are now reporting dependency conflicts attempting to install.It looks like they forked their own library to
gql-next
which uses the newer graphql-core library and is only supported on 3.6+. The original gql library seems to support a wider range of language versions, but is less type-safe (this is the library we originally developed on)