Vsevolod Tolstopyatov

The problem is even worse because it seems like we cannot track the job and consider such context changes meaningful because they can **potentially** race with each other. Racy example...

It works as expected, `ignoreUnknownKeys` is designed to ignore unknown _keys_, not values. But you can use `coerceInputValues = true` for the very purpose you described

Currently, the only workaround is to write your own serializer. We may consider implementing this functionality as part of `coerceInputValues`

We don't see much demand for it and are mostly focused on common solutions (i.e. `okio` integration) that cover the similar use-case for all the platforms rather than on a...

It's already been in the library since 1.4.0: https://kotlinlang.org/api/kotlinx.serialization/kotlinx-serialization-json-okio/ 😄

@sandwwraith this is a bug in the compiler plugin: ``` @Serializable data class Example(val value: String) @Serializer(Example::class) object ExampleSerializer ``` In this example, `Example.serializer().descriptor` and `ExampleSerializer.descriptor()` have different structure. Please...

I know, I've deliberately exposed it. Auto-generated serializer in nested companion (`@Serializable data class ...`) and auto-generated **external** serializer (`@Serializer(Example::class)`) have different SerialDescriptor structures. Two bugs here: 1) These descriptors...

We are on it; but it might be the case the fix requires a compiler version update though

Note that obtaining the serializer via `serializer()` is not an option because it does not work on JS and K/N

Few more use-cases from Fleet: * IDE is configured in JSON format (the most common one and easy to parse/highlight), but users leave comments on specific tweaks. For that, Jackson...