Serde VS kotlinx.serialization

In PHP there is a lib that draws inspiration from serde https://github.com/Crell/Serde

Guzzle for the actual connection. Get back JSON. Use https://github.com/Crell/Serde to map that JSON into classed objects. Do as you will with the objects. (You can also do the same the other way around to create a message object with all the type safety and builder functionality you want, Serde it to JSON/array, and then send the message through Guzzle.)

I even have a very nice library to make that dead simple for you: https://github.com/Crell/Serde

Sounds a lot like Serde. :-)

Sounds a bit like Serde: https://github.com/crell/serde

Have you tried this:? https://github.com/Kotlin/kotlinx.serialization/blob/master/docs/serializers.md

Regardless, I followed the documentation to register List for polymorphic serialization and my static code analysis does not seem to be happy with it.

I think kotlinx.serialization might come close, but looks like custom Encoders and Decoders are still experimental.

This example will not work on a multiplatform project. you are using gson, gson runs only on jvm, you should use https://github.com/Kotlin/kotlinx.serialization for the json parsing

This is the issue to +1 https://github.com/Kotlin/kotlinx.serialization/issues/1931

Fun fact, kotlinx.serialization had a release just recently which makes it come with some bundled proguard rules to make this experience easier. Yes you'll still have issues if you're using things via reflection and try to serialize things that proguard deemed unused and removed them, but it's a step forward https://github.com/Kotlin/kotlinx.serialization/releases/tag/v1.5.0-RC

Kotlin Serialization

Kotlin Serialization is also a newer option, but doesn't have as much traction.

``` see the docs