feat: v0.20.0 — expose exact GraphQL response bytes - #31
Open
scarver2 wants to merge 1 commit into
Open
Conversation
scarver2
force-pushed
the
feat/exact-response-payload
branch
from
August 18, 2026 02:28
77acdce to
6e582bc
Compare
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
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.
Summary
ResponseEnvelope#response_payloadand bounded contact pagesGraphqlClient#envelope_from_response_payloadandContacts#page_from_response_payloadreplay seamsto_hserialization and inspectionpreserve_rawsupportSecurity boundary
Test plan
bundle exec rspec— 783 examples, 0 failuresbundle exec rubocop— 226 files, 0 offensesprintavo-ruby-0.20.0.gemgit diff --checkCloses #30
No gem publication is authorized by this PR. Sheriff release authorization remains a separate gate.
🤖 Generated with Codex