fix: don't strip empty arrays/objects - #391
Merged
Merged
Conversation
Jeremy Hinegardner (copiousfreetime)
approved these changes
Aug 11, 2026
This file contains hidden or 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
2 participants
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.
Description
Empty arrays/objects are valid JSON and we should respect what the user passes. This is necessary for a niche UPS option that needs an empty array passed on the request which was previously being stripped
Testing
Tweaked a test and investigated cassette output. Previous to fix got 500 and stripped value, now empty array is passed through.
Pull Request Type
Please select the option(s) that are relevant to this PR.