Also here https://www.http4k.org/ecosystem/http4k/reference/json/ i read "We have found KotlinSerialisation is possibly the least friendly to use in the context of http4k" -- I'm using it everywhere (db row mapper, JSON in and out) so far and seems to be holding out well. May I ask what is better in other solutions? Or how did kotXser hurt?
a
Andrew O'Hara
04/04/2026, 2:02 AM
It works fine. It just requires you to register custom adapters the Kotlinx way, and not with http4k's
AutoMappingConfiguration
. If you use
values4k
classes, you have to build your own adapters rather then use the builtin adapters.