Add #[serde(skip_serializing_if = "Option::is_none")]
to all fields
#79
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.
Hello,
I think it would be nice if there weren't any
null
values in my serialized data. After all, if I understand the spec then those keys are not present in the database that the library read, so I feel like it would be best if they were not present in my serialized output at all.I am unaware if there's a cleaner way to apply the serde attribute other than repeating it like this.
Please let me know if this makes sense or if you want any changes made. Thank you!