Leonid Startsev
Leonid Startsev
A `KSerializer` should serve the same purposes that `Nothing` in type system: indicate that a particular item should never be serialized. There are several use-cases for it, mainly connected with...
Originally reported as https://youtrack.jetbrains.com/issue/KT-52300 **To Reproduce** ```kotlin val descriptor = buildClassSerialDescriptor("FooBar") { isNullable = true } assertTrue(descriptor.isNullable) // throws ``` **Expected behavior** Either we should allow to create nullable descriptors...
We don't have any serialInfo-related information in our guide, and KDoc for it is rather scarce. Such nuance causes confusions like this: https://github.com/Kotlin/kotlinx.serialization/issues/1923
Now, we look up serializers for non-sealed interfaces in SerializersModule first, and only then unconditionally return PolymorphicSerializer. This is done because with old behavior, it was impossible to override interface...
**What is your use-case and why do you need this feature?** Currently, Properties allow to parse `Map` object to a Kotlin class. Usually, such properties are loaded from configuration file....
This will address: #66, #204 and #251. `kotlinx.io.core.Input/Output` should replace `ByteArray`s and `String`s in Binary and String formats, thus allowing to work with streaming API and easily convert content to...
**Describe the bug** `"type":"kotlin.collections.LinkedHashMap"` is an incorrect discriminator and prevents data from de-serialization **To Reproduce** ``` @Serializable data class ValueHolder( val someField: Int, @Polymorphic val value: V, ) @Serializable data...
See the https://github.com/Kotlin/kotlinx.serialization/issues/1533 for context
JVM works since 1.8.0; Native should work with 2.0.