Add strict parsing for RequestOptions #901
Merged
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
Merged
remi-stripe
approved these changes
Mar 24, 2020
ob-stripe
added a commit
that referenced
this pull request
Mar 24, 2020
ob-stripe
added a commit
that referenced
this pull request
Apr 3, 2020
richardm-stripe
pushed a commit
that referenced
this pull request
Apr 24, 2020
ob-stripe
added a commit
that referenced
this pull request
May 1, 2020
richardm-stripe
pushed a commit
that referenced
this pull request
May 11, 2020
richardm-stripe
pushed a commit
that referenced
this pull request
May 14, 2020
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.
r? @remi-stripe
cc @stripe/api-libraries
Add strict parsing option to
RequestOptions::parse(). When enabled, strict parsing will throw anInvalidArgumentExceptionwhen:['api_key' => 'sk_...'])Strict parsing is disabled by default, but is enabled when used from
StripeClient. This makes this change fully backwards compatible for existing request methods on models, but forces strict parsing when using request methods on services.