This repository has been archived by the owner on Nov 28, 2022. It is now read-only.
Fix problem where nested objects would appear empty #180
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
On production right now if there's a nested object in a form, it always get
in the code sample even if the form values are not set:
```
--data '{"category":{}}'
```
This PR recursively removes empty objects from the form values so they
do not get set when making the request.
This problem was slightly exacerbated by #179 which auto applied default
values from the form to the samples.
mjcuva
approved these changes
Dec 13, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
On production right now if there's a nested object in a form, it always get
in the code sample even if the form values are not set:
This PR recursively removes empty objects from the form values so they
do not get set when making the request.
This problem was slightly exacerbated by #179 which auto applied default
values from the form to the samples.