GuzzleHTTP 7 compatibility #5
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
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.
Hi,
I had to use this library in a project recently and it was using an old version of the graphql-client library that relied on GuzzleHTTP 6.x. This is quite an old release of Guzzle and it conflicted with the newer GuzzleHTTP 7.x I was using.
I've bumped the graphql-client to a newer version in this PR which does support 7.x of Guzzle. They unfortunately haven't made a release, so I've pointed it to
dev-masterfor now. It does retain compatibility with Guzzle 6.x though so existing installs shouldn't be impacted. The SDK still appears to be working as expected with this new version.