fix: ensure JSON in form-data field is parsed IFF it is an object or array #730
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
|
Hi, some time has passed and this is still an issue in version 5. |
cdimascio
approved these changes
Jan 10, 2023
|
hey not to bug you @cdimascio but would be great if we could get a release with this fix 🙏 |
|
Will have it out momentarily. Thanks for the reminder |
|
Available in v5.0.2 |
|
Awesome, thank you man! |
This was referenced Jun 24, 2024
This was referenced Aug 26, 2024
This was referenced Sep 15, 2024
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 commit fixes a problem with non primitives values in multipart/form-data field(s).