Add sanitized_params option to allow disabling sanitization #973
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
|
I'd suggest we start with #1008 , and then see if it's still a problem for folks still using openapi2. |
|
I'm fine with #1008 instead, as its probably the more correct way to handle this. When I get a chance I'll test the other PR and see if it addresses our issue. You mentioned openapi2 but we were affected by this in openapi 3. |
|
Is this still needed after merging #1008? |
|
I'm pretty sure #1008 resolves this, so I'll close it for now. |
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.
Fixes #835 .
Changes proposed in this pull request:
This is useful when the keys in a JSON post body contains characters like
-or$