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
@Incara At this point I think it gets included by default, since there are cases where base type is concrete and usable. It is even possible there might be actual value deserializer (at least in theory).
So I am not 100% sure if it'd be possible to remove it -- but at this point it will be included and there is nothing you can do to remove it from being considered valid (although attempt itself would fail unless there's static factory method producing some subtype).
cowtowncoder
changed the title
Abstract class included as part of known type ids when using JsonSubTypes
Abstract class included as part of known type ids for error message when using JsonSubTypes
May 6, 2020
I have the below class definition:
When attempting to deserialize, if I specify the wrong property, I receive the correct error stating:
Could not resolve type id 'string' into a subtype of [simple type, class SomeClass]: known type ids = [SuperType, subType1, subType2, subType3]
However, I want to know why my SuperType considered a known type id? Is there anyway to exclude it since it is an abstract class?
The text was updated successfully, but these errors were encountered: