kotlinx.serialization
kotlinx.serialization copied to clipboard
Kotlin multiplatform / multi-format serialization
Right now, the failure is the following: ``` Exception in thread "main" kotlinx.serialization.json.internal.JsonDecodingException: Unexpected JSON token at offset 20: Encountered an unknown key 'version' at path: $.name Use 'ignoreUnknownKeys =...
Section https://github.com/Kotlin/kotlinx.serialization/blob/master/docs/formats.md#custom-formats-experimental should also explain how to properly use `SerialDescriptor.getElementDescriptors()` to write a schema generator if you're authoring a serialization format with a schema.
I ran the code below and couldn't figure out why the output is behaving this way. The Code: ```kotlin import kotlinx.serialization.ExperimentalSerializationApi import kotlinx.serialization.properties.Properties import kotlinx.serialization.properties.encodeToStringMap @OptIn(ExperimentalSerializationApi::class) fun main(): Unit {...
**What is your use-case and why do you need this feature?** I'm currently working for the avro4k library that is the implementation of avro format with this powerful kotlin serialization...
If I want to define a class hierarchy of small serializable classes, the `@Serializable` annotation can become painfully redundant. This can make the code at worst twice as long, and...
**What is your use-case and why do you need this feature?** `JsonDecodingException: Expected class kotlinx.serialization.json.JsonObject (Kotlin reflection is not available) as the serialized body of F, but had class kotlinx.serialization.json.JsonLiteral...
**Describe the bug** I have the suspicion that the incorrect SerialName is used when using a delegate serializer on a class implementing a sealed interface. This could just be a...
There are multiple places within the library where the data is included in exception messages. Not only might this data be dangerous in certain situations, it might also contain sensitive...
It is necessary to configure Kover in such a way that it is possible to verify the coverage of individual modules. The main problem is that many modules do not...
It is here from 1.3, we get the overall positive feedback and there is not many reasons to keep it experimental any longer