This is probably a layer 8 problem, but I'm stumped. I'm attempting to use kotlinx.serialization without taking a kotlin-reflect dependency in a multiplatform project. I'm trying to do a basic sanity check in a JVM unit test that this works, but am getting a

NoClassDefFoundError

in

Json.<clinit>

, which is indirectly trying to look up

KPackage

, a kotlin-reflect type. The test passes if I add a

kotlin-reflect

dependency. Is it the case that json support requires kotlin-reflect?

(it's building a

Map<KClass<*>, KSerializer<*>>

, which I believe does in fact require kotlin-reflect to materialize the entire KClass.

Are there any common ways of converting a

KClass<T>

+ `value: String`into an instance of

T

, given that you know

T

is a reasonable value type (

Double

,

Int

,

Enum

, or

String

)?

I have a

Map<String, Any>

and one of the values contains a

Date

instance. Is it possible to have a custom serializer in this case? In

deserialize

method I don't know how to decode it

can i not serialize `object`s ? it seems to not work in Polymorphic code in :thread-please:

Hey all. I'm trying to use this data class and getting this response:

j.b.u: Can't locate argument-less serializer for class e.b.b.d.a (Kotlin reflection is not available). For generic classes, such as lists, please provide serializer explicitly.

Can anyone confirm that this means I have to write my own serializer because it's using a

Map

? Or is there a way to do this that I'm missing somewhere? I'm using this with a Ktor request.

Might be a strange question but how do you write a serializer for

kotlin.Result

class? Let say I want to write a custom call adapter for Retrofit that wraps all my requests in

Result

class. Right now serialization converter is failing with

Can't locate argument-less serializer for class kotlin.Result

which sounds reasonable. How would one workaround this situation?

Hi all, does anyone know how to make a

JsonConfiguration(classDiscriminator = "customType")

work only for a particular class? For instance, let’s say I have something like:

@Serializable
data class MyClass(
  @Polymorphic
  val polymorphicA: PolymorphicA,
  @Polymorphic
  val polymorphicB: PolymorphicB
)

And I’m serializing/deserializing an instance of

MyClass

. I want to serialize/deserialize

polymorphicA

using the default

classDiscriminator

which is

type

. However, I want to serialize/deserialize

polymorphicB

using a custom

classDiscriminator

, say

customType

. I don’t think the steps outlined in https://github.com/Kotlin/kotlinx.serialization/blob/master/docs/polymorphism.md#a-bit-of-customizing showcase that level of granularity (i.e. if a custom

classDiscriminator

is specified, it’s applied to all of

MyClass

, which is not what I want).

Hi everyone! Does anyone know if https://github.com/Kotlin/kotlinx.serialization is the offical repository for this project? I'm trying to find out if using kotlinx.serialization is viable in the long term. We're stuck on kotlin 1.3.31 due to issues with kotlinx.serialiation in our multi-platform project and I have no idea if/when they will be resolved. There are no answers in the github issue tracker for the problems that affect us. I was wondering if there is a better place to report issues since there is not much dev activity in the repository or issue tracker on github.

What do you do if you want to have a “summary” version of the same model, with the summary being the super class of the full model? I’ve got issues with constructor parameters not being properties etc

Hello. I'm trying to set up my Multiplatform project with Ktor and Kotlinx.Serialization. I see for Native code there is an artifact for each specific Native target, and also just a "native" one. Just wondering which one I should be using for my targets-- if I have to use each specific one or if I can just use the "native" artifact?

Is there any documentation on creating add-on formats for kotlinx.serialization? It looks like there are some community made additional formats.

I'm deserializing a

Date?

from a

String?

using a custom

KSerializer<Date>

and it's working great, until the 3rd party API I'm using sends an empty string instead of null as expected. Is there a way to map this empty case to a null Date instead of a dummy-Date? It seems something like

KSerializer<Date?>

is not supported, is that correct?

OK, I am continuing struggle with custom serializers. I am building my own analog of PolymorphicSerializer for a class which explicitely contatins type of the value and then the value itself. Everything works, but the problem is that if I follow the examples, then the field which contains actual value lacks the descriptor. Is there a way to generate sum-of-types style descriptor for that field?

I got stuck again with custom serializers. I have a rather simple external object, which has three number fields: x, y and z and I want to create a custom serizer that replaces zeros with missing values and vice versa. Here is what I've written. It produces correct output, but refuses to read because it expects additional openning

{

inside the object. What am I doing wrong?

But I got this exception at build time:

e: java.lang.AssertionError: Recursion detected on input: IMPORT_DIRECTIVE under LockBasedStorageManager@160c4e98 (TopDownAnalyzer for JVM)

Is there still no support for serializing objects? Like the questions in these messages: https://kotlinlang.slack.com/archives/C7A1U5PTM/p1551795255021700 https://kotlinlang.slack.com/archives/C7A1U5PTM/p1570900761010800

i have problem when using type aliases for Map<String, List<String?>> .. i get a weird indexoutofboundsexception .. but it works when i just use the map. i know i found a ticket somewhere about this problem .. but i can't find it anymore. any ideas if this is going to be fixed soon?

Hey there! What is the easiest way to parse an ISO8601 date right now with kotlinx serialization?

This message was deleted.

Hello. Today I have seen that Kotlin 1.3.60 was released and, as I remember, it is expected that Kotlinx serialization will have a new one version after 1.3.60 version release. Is there some information about dates of new release for kotlinx.serialization ?

📣 kotlinx.serialization

0.14.0

has been released! This release contains some breaking changes and requires Kotlin 1.3.60 to work on all platforms. Some highlights: • Support for tvOS and watchOS in all flavours (added in Kotlin/Native 1.3.60) • Special support for serializing Kotlin's `object`s and

sealed class

es. See updated docs: https://github.com/Kotlin/kotlinx.serialization/blob/master/docs/polymorphism.md#sealed-classes. • Enums now should support

@SerialName

and other specific annotations (but they should be marked

@Serializable

). Full changelog: https://github.com/Kotlin/kotlinx.serialization/blob/master/CHANGELOG.md#v0140--2019-11-19

> Special support for serializing Kotlin’s

object

Is there any example on this theme? What is use case for

object

?

So I’m working with an API that represents money as a decimal number in JSON, e.g.

"amount":10.99

. How would i serialize a

BigDecimal

or

String

representation to a JSON number without any intermediate conversion to a floating point number?

Hello:) Is it possible to decode json element (especially - jsonobject) inside of deserialize method of serializer even when decode was not created inside Json StringFormat?

Hi, in a Kotlin MPP, is there a clean way of serializing a Map<String, Any> to a JSON string? I've tried doing it using kotlinx.serialization but it seems to support only classes annotated with @Serializable, am I missing something? Thanks 🙂

Using

DraftSource.build(actionId = 0, messageId = "id")

or also

as DraftSource

is failing with

Can't locate argument-less serializer for class

Can someone tell me whats wrong? It looks like the serializer doesnt recognize my Map<String,String>. Im getting an

java.lang.InstantiationError: kotlinx.serialization.KSerializer

error. Even when I use the Data(abc) nesting example from <https://github.com/Kotlin/kotlinx.serialization/blob/master/docs/examples.md>

if enum classes are inherently serializable, why doesn't it inherently have

MyEnumClass::serializer

? should I annotate

@Serializable
enum class MyEnumClass { ... }

so that I can access it?