Except for id, message and name none of the other fields will be mapped correctly. As StatusMessage is being used by a variety of fields, before I attempt to fix it, I was wondering what approach would you like to take?
I saw a Generics 1.18 ticket so not sure if this would benefit from it.
I was thinking of a few approaches.
Parse the the message twice giving it raw JSON and a 2nd time with just the content of datasource ?
Create a new DatasourceStatusMessage.
Look at how Generics might come into play to create a more generic approach.
Any suggestions on how you'd prefer to have this handled?
Hello,
The response for the current version of the API looks like this for: Version 8.3.6
Except for id, message and name none of the other fields will be mapped correctly. As StatusMessage is being used by a variety of fields, before I attempt to fix it, I was wondering what approach would you like to take?
I saw a Generics 1.18 ticket so not sure if this would benefit from it.
I was thinking of a few approaches.
Any suggestions on how you'd prefer to have this handled?