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.
r? @bkrausz @jimdanz
Add support for
Stripe-Account
header inRequestOptions
.This can currently only be used on methods with
RequestOptions
as the final parameter in their signature (none withString apiKey
).There's no tests because there's no way to test the existence of the headers without creating new accounts (if the real API is to be used, in the style of the existing tests) or ripping a lot of things apart (if mocks/captors are to be used). I tested using my own account + a test account in a super simple program:
and verified that it returned charges from the connected account.
The issue of testing seems like too big to shave right now, and I'm pretty confident in the correctness of this.