ksp VS kotlinx.serialization

google/ksp is one of the lightweight compiler plugin. We can easy to create compiler plugin with simple syntax. It's set as stable last year.

google/ksp is one of the lightweight compiler plugin which is developed by google. Some jetpack libraries are supporting that configures with ksp (ex: room).

Some guys consider it as a bug.https://github.com/google/ksp/issues/969

Links: GitHub Repo : https://github.com/aniketbhoite/ksp-my-event Google KSP Doc: https://github.com/google/ksp KotlinLang KSP Doc: https://kotlinlang.org/docs/ksp-overview.html

If you ever come back to it, check out https://github.com/google/ksp, it's relatively new but I think it might be a great fit for the project.

Fyi ksp handles tracking this for incremental builds, you may be able to see what they are doing?

I'd like to further iterate on all these patterns in some form of codegen library in the future, as compiler plugins start to mature. I'm hopeful for a multiplatform version of Kotlin Symbol Processing to help with this, though this won't be possible before Kotlin 1.5.20 at the earliest due to missing extension points in the Kotlin compiler. Fingers crossed for something this summer I guess.

Well, KSP is developed by Google, so you should ask them for more documentation, I think :) For compiler plugins -- yes, JetBrains should at some point invest some time and create at least the basic documentation for compiler plugin authors. But first of all, we need to create the public compiler API itself. We are going to do that after releasing the JS IR back-end.

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