In this case due to hash merging order relationships always take precedence over attributes,
so the deserialized attribute invoiceType in the case above will be invoice instead of expected prepayment.
The fix may be as easy as switching the order for deserialize_rels and deserialize_attrs
There is an issue in case payload deserialization like this happens:
In this case due to hash merging order relationships always take precedence over attributes, so the deserialized attribute
invoiceType
in the case above will beinvoice
instead of expectedprepayment
.The fix may be as easy as switching the order for
deserialize_rels
anddeserialize_attrs
though it's not backwards compatible.
Please suggest, Leo