Fix serialization of properties holding None values #85
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.
The current implementation fails to serialize properties holding the value None. This may not affect al types of field as it depends how the field handles its conversion in its Field.to_representation() method. At least with datetime fields the attempt to serialize a None value will result in an AttributeError -- see the following stacktrace:
This pull request addresses this issue by calling the to_representation method only when there is an actual value to convert.