Is there way to overrider json key that is respons...

# serialization

[Eugen Martynov]

Is there way to overrider json key that is responsible for the sealed class serialisation pick up?

[Eugen Martynov]

I wrote JsonContentPolymorphicSerializer it works great for deserialisation however, it doesn't write field during serialisation

[Paul Woitaschek]

https://github.com/Kotlin/kotlinx.serialization/blob/8be6845927414a844ffebedc871dd8bc0d4b8aee/core/commonMain/src/kotlinx/serialization/SealedSerializer.kt#L105

It's hardcoded

[Eugen Martynov]

Yeah, I know it. So the only way it is to write completely new serialiser in this case

[Eugen Martynov]

What if I try to override descriptor? Or descriptor is only used to pickup correct serialiser and is not used during serialisation?

[Paul Woitaschek]

One Idea I have is to maybe utilize the JsonTransformingSerializer and rewrite the type field

[Paul Woitaschek]

Might be worth a shot

[Eugen Martynov]

Super thank you!

[Eugen Martynov]

It looks like really a hack. I probably will just write a staightforward serialiser and talk to BE people to ask use type for such cases

[Paul Woitaschek]

https://jsonapi.org/

[Paul Woitaschek]

Seems to be some kind of a standard

[Eugen Martynov]

Thank you!

[Paul Woitaschek]

@Eugen Martynov
Look what I found in a PR I was reviewing 😛
https://github.com/Kotlin/kotlinx.serialization/blob/master/docs/json.md#class-discriminator

[Eugen Martynov]

🙂 Great!!! I still need ask for the consistency from backend people. Otherwise I have to find a way how to tweak Json for every specific case. Here is also interesting decision - it is rather connected to the deserialization and not class itself.

[Paul Woitaschek]

Yeah I’d make a very strong case for sticking to the convention

[Eugen Martynov]

There is the way! @JsonClassDiscriminator

[Paul Woitaschek]

That one is well hidden :)

[Eugen Martynov]

And if you have consistency in your BE you can do it with

Json {
   classDiscriminator = "out_type"
}