Fix stripe-context not being included in subsequent list requests
#1660
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.
Why?
Fixes a bug where the
stripe_contextproperty wasn't correctly persisted when making requests in an auto_paging_iter call. As a result, the first API call of a list would work, but subsequent pages wouldn't includestripe_contextand could fail / use the wrong context. This was only an issue withstripe_context;stripe_accountwas unaffected.What?
"stripe-context"in the list of persisted keys_replace_optionsto_new_requestor_with_optionsto better describe the methodSee Also