Update graphql request to 6.x #228
Open
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
|
@ribeirojose Thank you for your PR. Can you rebase your branch? |
ribeirojose
force-pushed
the
update-graphql-request
branch
from
586a129
to
04e6a05
Compare
|
done 👍 @eitoball |
|
@ribeirojose Thank you for rebasing. Can you fix the following failing spec? |
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Updates graphql-request to ^6, and use the types published with the package.
What is the current behavior? (You can also link to an open issue here)
Use graphql-request ^4.
What is the new behavior (if this is a feature change)?
Use graphql-request ^6;
when importing the "ClientError" type, import from "graphql-request" directly.
Other information:
depends on update pkg version to match published in NPM (0.8.5) #227