Backwards compatibility break in serialisation engine when deserialising nullable fields

Description

Seems like the serializer in V3 handled deserialization of nullable fields where the field was null, presumably it assigned some default value to the field. However, in V4, the behaviour has changed and this case is not handled anymore and instead an exception is thrown... which is what you can see in https://r3-cev.atlassian.net/browse/R3T-2225.

Assignee

Dominic.Fox@r3.com

Reporter

Roger Willis

Labels

None

Sprint

None

Epic Link

None

Priority

Highest

Engineering Teams

None

Fix versions

Affects versions

Ported to...

None

Story Points / Dev Days

None

Build cut

None
Configure