As of https://github.com/spring-projects/spring-framework/issues/35733, Spring Framework has a dedicated method for configuring a Kotlin Serialization converter specifically.
We should reflect that in our DefaultClientHttpMessageConvertersCustomizer to use this new method.
Comment From: bcmedeiros
I was just about to ask what would be the impact in Boot after the Framework change, and I saw this issue.
if an application has Kotlin Serialization on the classpath, it is expected to use a dedicated converter for serializing @Serializable types.
Is the newly introduced starter still going to be needed after this ticket is addressed? I understood just having the library in the classpath was not enough, but after this comment in the framework issue, I'm a bit unsure about the starter actually doing anything.
Comment From: bclozel
@bcmedeiros yes this change is still required and the dedicated module is important: this is what allows you to use configuration properties to drive the creation of the Json instance and the Kotlin Serialization converter itself.
Comment From: wilkinsona
As part of this, we should remove @Order(-10) // configured ahead of JSON mappers from the Kotlin converter's @Bean method.
Comment From: dmitrysulman
@bclozel Can I work on this issue?