How hard is it to switch openapi generator from ja...

# http4k

[plastiv]

How hard is it to switch openapi generator from jackson parser?

I think currently the optimization tradeoffs between different parsers https://www.http4k.org/guide/howto/make_json_faster/ are down to: do you want openapi integration? If yes - parser decision has been maid.

Even when serializing responses with something like kotlinx.serialization the jackson is on classpath with all it's tradeoffs and benefits anyways.

[s4nchez]

The switch can be done by setting a different apiRenderer in OpenApi3 class. Here's an example for Kondor

[plastiv]

Thanks for the pointer, will check

[s4nchez]

I agree that one should try to leverage whatever JSON library they're already using for the OpenApi bit. However, both OpenAPI spec and JSON libraries have their own idiosyncrasies which may require some effort to work around

[plastiv]

OpenApi3KondorTest example turned out harder to follow than I thought 😓 I wanted to check if I can use kotlinx.serialization for openapi generator and looks like not today 😅