You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will throw right on adding the mapper. I guess this is because there is a [CborConstructor] attribute and there won't be, for example, a "r" or "s" to deserialize, could you just add null, or allow an option to not throw if not all fields can be deserialized?
Or can I use more than one [CborConstructor] and build multiple constructors for each case? (I got different (de)serialization modes and need to be able to serialize one single class in different ways)
The text was updated successfully, but these errors were encountered:
mcatanzariti
changed the title
[bug] Issue with ObjectMappingRegistry if used alongside attributes
[enhancement] support non default constructors with non mapped parameters
Sep 1, 2019
Consider this example:
And this filter approach:
This will throw right on adding the mapper. I guess this is because there is a [CborConstructor] attribute and there won't be, for example, a "r" or "s" to deserialize, could you just add null, or allow an option to not throw if not all fields can be deserialized?
Or can I use more than one [CborConstructor] and build multiple constructors for each case? (I got different (de)serialization modes and need to be able to serialize one single class in different ways)
The text was updated successfully, but these errors were encountered: