[Dynamic or “Per class” classDiscriminator ?]
r
[Dynamic or “Per class” classDiscriminator ?]
message has been deleted
Given the example above: I can either set the
classDiscriminator
to
conversation_type
or
profile_type
and that will only result in one of the json strings being encoded/decoded correctly. However, the json instance needs to be able to handle both discriminators. Is there any way to accomplish this? Maybe per top hierarchy class annotation or dynamically ?
d
There's an issue open for this.
r
Ah, lovely. Thanks for the link. I will catch up with it.