#128 Allow specifying empty lists of maps #133
Draft
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.
Currently, toBody() does not distinuish between list-of-maps attributes
being null and empty.
This results in the provider omitting the attribute from the API request
when the value is an empty list,
making it impossible for the user to clear a list of maps.
Handling of lists of primitive values like strings
does not have this issue -
attributes with an empty list value are included in the request
while ones with a null value are skipped.
Change the check to only omit list-of-maps attributes with null values.
TODO: Only
appliance_security_malwarewas tested. Test most of the other resources.TODO: Change
organization_extensions_thousand_eyes_networkcustomized code as well?Fixes #128