Add fos_rest.serializer.serialize_null to control null value serializati... #480
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 JMS serializer by default will not serialize keys with a null value.
This new parameter allows control of this behavior via the FOSRestBundle
configuration in app/config/config.yml.
Setting fos_rest.serializer.serialize_null to true will cause the
setSerializeNull() method on the Context object to be called with the
value that is set in the configuration.
Add test case to check that the Context Object has its member
$serializeNull set to the correct value.
Add new parameter to the Resource/doc/configuration-reference.md
documentation file.