Hello. Is there a way to make the HttpClient JsonFeature reuse the same serializer/mapper we have co...

# ktor

[anthony castillo]

Hello. Is there a way to make the HttpClient JsonFeature reuse the same serializer/mapper we have configured for the server?

[Dico]

Share the code that creates the mapper between both modules using a shared module or copy it

[anthony castillo]

so here we create a common mapper to be used by our application:

val mapper: ObjectMapper = jacksonObjectMapper()
    .configure(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES, false)
    .setSerializationInclusion(JsonInclude.Include.NON_NULL)

then we set it as a part of content negotiation feature

install(ContentNegotiation) {
        register(ContentType.Application.Json, JacksonConverter(mapper))
    }

however, we are unable to use the same mapper for HttpClient

val defaultHttpClient = HttpClient(OkHttp) {
        expectSuccess = false
        install(JsonFeature) {
            this.serializer = JacksonSerializer {
                configure(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES, false)
                setSerializationInclusion(JsonInclude.Include.NON_NULL)
            }
        }
        engine {
            config {
                readTimeout(Duration.ofMillis(2000))
                connectTimeout(Duration.ofMillis(5000))
                connectionPool(ConnectionPool(100, 1, TimeUnit.MINUTES))
            }
        }
    }

[anthony castillo]

would be nice to be able to pass the mapper as well

[Dico]

Have a function that configures ObjectMapper instead

[Dico]

function ObjectMapper.configureContentNegotiationFeatures() { setSerializationInclusion(...) }

[Dico]

And call it from server and client

[anthony castillo]

thank dico. yeah we had to do something like this. would be convenient though if mapper can just be passed