Leonid Startsev

Duplicate of #1264

Sorry, I don't quite get the idea. You mean that you want inline classes to be serializable as regular classes, without any inlining?

As for now, there is sufficient demand and use-cases to provide an option to globally disable type discriminator (NEVER option) — mainly, to interact with external API that has validation...

The point about Spring and other frameworks is a really good one, thanks. Even Ktor has the same problem. It's still possible to use `convertAndSend("/some/destination", someObject)`, but this is a...

While discussing `POLYMORPHIC_SUBTYPES` internally, we stumbled into the design problem of when this flag should be applicable. Problem described in initial ticket happens only on 'top-level' serialization: when you call...

@wman1980 We now have `coerceInputValues` key in Json that allows using default value for unknown enum element. Is this sufficient for your case? If not, custom serializer you mentioned should...

I think `RealmList` should have some kind of `asList` view function, doesn't it? In this case, you can delegate to ListSerializer roughly like this: ``` class MyRealmListSerializer(val tSer: KSerializer): KSerializer...

Again, you can use `SerialDescriptor(serialName: String, original: SerialDescriptor)` function to wrap `ListSerializer(tSer).descriptor)`

Related: #1169 Btw, in your case It is worth looking into [json transformers](https://github.com/Kotlin/kotlinx.serialization/blob/master/docs/json.md#json-transformations) rather than full-blown custom serializers

I think nullable JsonTransformingSerializer is a separate issue, can you please create one?