Fix Field#properties_to_hash method #192
Merged
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 the Field class, when converting the properties to a hash for sending the API request, the method is not avoiding empty values (it does already avoid them when serializing validators).
These cause some requests to fail when trying to creating new content models using an existing (from another model) complex (array or referenced) field as the source.
This small change fixes the issue and allows for complex content model migrations or duplication.
Before:
With this fix: