Include empty arrays for components/inputs/outputs on JSON Serialize #78
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 (per the included unit test) if you have an empty components array
"components": []
on serialization to JSON we remove this array. This make processing the structure downstream more complex.Sadly Golang doesn't let you omit
null
, but include the empty array -omitempty
zaps both of them (encoding/json/v2
will solve it if it comes along).So this PR proposes we are more verbose on serialization and always include
"components":null
rather than when we round-trip an omitted array, and"components":[]
when we round-trip an empty array.This makes
components
consistent withinputs
andoutputs
.