Repository navigation
Support explicit offset in PricingRead.get - #62
Merged
Merged
Conversation
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.
Scope
Append optional
offset=NonetoPricingRead.get, preserving positional limit, omitted defaults, complete response envelopes and Decimal decoding. Validate explicit offsets consistently with limits; send one request without automatic traversal.Verification
Eight focused regression tests; finite offline suite increases from 208 to 216. Exact independently reviewed three-file candidate; dependencies and workflows unchanged. Local Python 3.12 source suite: 216 PASS. Hosted installed-wheel Python 3.10/3.11/3.12 qualification required before merge.
No arbitrary filters, pricing calculations, provider compatibility, release qualification or whole-operation completeness claim.