how can I do a sealed class that contains a data class and a

Question

how can I do a sealed class that contains a data class and a String that s for a Json file where I can have either of these two

Ruckus · Answer

You can t but you can make a wrapper for `String`

Ruckus · Answer

``` sealed class Json lt T gt val value T class JsonElem value String Json lt String gt value class JsonArray value List lt Json lt gt gt Json lt List lt Json lt gt gt gt value class JsonObject value Map lt String Json lt gt gt Json lt Map lt String Json lt gt gt gt value ```

bjonnh · Answer

I have to see if Moshi handles that

bjonnh · Answer

thx

kevinmost · Answer

You can use custom adapters in Moshi to serialize it however you want

bjonnh · Answer

yes that s what I am trying but I have issues wrapping my head around how I m supposed to get something that can return one of the two types

bjonnh · Answer

< kevinmost> do you have any reference for moshi where polymorphic is applied to a type inside a file

bjonnh · Answer

I can only find examples where it is polymorphic on file

kevinmost · Answer

generally to make polymorphic JSON you d have some sort of type string to go along with the actual data object and you d switch on that string to determine what serializer deserializer logic to use

bjonnh · Answer

yeah in that format that I don t control I get query foo to bar OR

kevinmost · Answer

I m not too familiar with Moshi honestly but Gson s TypeAdapterFactory would let you peer into the JSON before you decide what logic to use

bjonnh · Answer

I should just switch my JSON lib then

bjonnh · Answer

it reminds me of all those web framework they all show you how easy it is to do a todo list and then they don t tell you that anything more complex will take you days of tweaking

kevinmost · Answer

you shouldn t do that Moshi can do everything Gson can and more What you re trying to do is not standard with JSON and thus is clunky to do in any framework JSON that s polymorphic without a type string sitting next to it is just objectively bad API design

kevinmost · Answer

you re gonna switch to Gson implement TypeAdapterFactory and realize that it s at least as weird via Gson as it is via Moshi

bjonnh · Answer

hmm

bjonnh · Answer

I wanted to handle that field for the sake of completeness I will probably just ignore it

sitepodmatt · Answer

dont forget to read the recent changelog moshi added a polymorphicjsonadapter for event sourcing not switched yet since I built my type adapter a while ago

bjonnh · Answer

thx What I m lacking mostly is really examples on how to use that