fix: decode GraphQL response when using the Guzzle HTTP client - #287
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #287 +/- ##
============================================
+ Coverage 95.10% 95.21% +0.11%
Complexity 2540 2540
============================================
Files 217 217
Lines 6959 6959
============================================
+ Hits 6618 6625 +7
+ Misses 341 334 -7 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
andrii-bodnar
approved these changes
Oct 1, 2026
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
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.
GuzzleHttpClient returns a PSR-7 stream, and GraphqlApi passed it straight to json_decode() under strict_types, raising a TypeError. Cast the response to string before decoding.