Open
Description
I've found an issue where a null value in an 'exotic' type from a third party library doesn't get deserialized correctly due to the settings for Json.NET.
I've posted a spike to my fork:
https://github.com/Simcon/memstate/commit/71870e91aad95a5a3d23bf6803b5b47b56c87501
Check out the addition of NullValueHandling = NullValueHandling.Ignore
to the JsonSerializerAdapter constructor. This fixes the issue in the corresponding test.
The simple fix is to add the fix to mainline. Would this be possible, @rofr ?
The 'right' fix would be to allow specifying serialization settings but this non-trivial as far as I can see.