Allow configuring Stripe-Version at the gateway level
#167
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
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.
This change allows setting the Stripe version header at the gateway level. We routinely parse out some of the additional data returned by Stripe in our application and require all requests to be tied to a specific version.
No additional tests are needed since
GatewayTestCase::testDefaultParametersHaveMatchingMethodsautomatically tests all default parameter getters and setters.This change expands on #136 (which only allows setting the version at the request level).
This possibly fixes #135.
This also supersedes / fixes #110 which appears to be stale due to #136.