Hello Anyone has exp with moshi when dealing with ...

# announcements

[Joaquim Ley]

Hello
Anyone has exp with moshi when dealing with different types on the same property?
My specific use case, I have a variable that sometimes returns an object and others a boolean 🤷‍♂️
I know this must be done with adapters but I haven’t been able to get it to work, since all the examples I read is from a int to bool or something like that, not primitive to object

Thanks in advance 💪

```

[Dominaezzz]

Code example? (Have you considered kotlinx.serialisation 😛).

[kevindmoore]

When using GSON, we just have 2 different nullable variables for each case. Not the best, but it worked

[Joaquim Ley]

object: {
  owner: "John Doe",
  price: false <--------- bool
},

(...)

object: {
  owner: "John Doe",
  price: { <--------- Object
      rate: 0.00420529425481,
      amount: 343
  }
},

(...)

[Joaquim Ley]

Here’s a small snippet to illustrate the use case, regarding kotlinx I haven’t used it as an adapter for retrofit so not sure if it is working, as for GSON it would a big change and possibly loose capability of the default values 😄

[kevindmoore]

I wanted to switch to Moshi but co-worker didn't want to change

[Dominaezzz]

Well, this looks like sealed class territory.

[kevindmoore]

Not sure if this helps: https://proandroiddev.com/moshi-polymorphic-adapter-is-d25deebbd7c5

[Joaquim Ley]

I’ve read, and re-read that article still haven’t been able to figure out,t his has to do with the Kotlin adapter which I’m unable to build a working solutions :S
@Dominaezzz don’t really get where sealed classes would be useful here?

[Dominaezzz]

What type do you want price to be?

[Joaquim Ley]

the object… and null if bool

[Dominaezzz]

Oh! Instead of using null, false is used.

[Dominaezzz]

I didn't understand that.

[Dominaezzz]

You can make a type adapter and check for "false".

[Joaquim Ley]

Thanks for your input but that’s exactly what I’ve been saying, if you read what I’ve said you can see what my use case is, I don’t get the sealed classes and checking for “false” would help. My issue is exactly with the adapter from boolean to object (the one I specify), I’ve been searching all over the interwebz and can’t seem to find a good solution :S

[kevindmoore]

I think what Dominic is saying is that by using a sealed class with a name of "price", you could have 2 different types: One that has a boolean value and another that has the items in your object

[Dominaezzz]

class PriceAdapter(val adapter: RealPriceAdpater) {
  @ToJson fun toJson(price: Price?): String {
    return if (price != null) adapter.toJson(price) else "false"
  }

  @FromJson fun fromJson(price: String): Price? {
    if (price == "false") return null
    return adapter.fromJson(price)
  }
}