Move request-sending functionality into a common place #1654
Conversation
This file contains 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
anniel-stripe
requested changes
Jan 13, 2023
|
Mostly questions! |
…into_a_common_place
anniel-stripe
approved these changes
Jan 13, 2023
remi-stripe
deleted the
pakrym/Move_request-sending_functionality_into_a_common_place
branch
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.
Currently all the request making logic in stripe-node resides in
StripeResource. We'd like to be able to make requests from arbitrary places without a resource object.This PR moves the request-making logic into
RequestSenderclass and place an instance of it onto the main Stripe client.This follows the pattern we have in Java with https://github.com/stripe/stripe-java/blob/master/src/main/java/com/stripe/net/StripeResponseGetter.java#L8