Updated KeyValuePairSerializer to allow null value #982
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.
Updated KeyValuePairSerializer (used by MapSerializer) to allow value to be null. It still makes sense to not allow null for key since that is a requirement of the C# Dictionary.
This change fixes an issue I saw while upgrading from V2 to V3. V3 didn't properly deserialize a Dictionary<> when the value in the KeyValuePair was null however this worked fine on version 2.4.4. I found that this only happened when deserializing as a Dictionary<> and if you deserialize as a KeyValuePair<> array it worked as expected. I tracked this down to the internal KeyValuePairSerializer.