A modern programming language that makes developers happier.

kotlinlang

What is the state of the art with OpenAPI support in http4k (specifically the schema)?
The current example-based generation is letting us down, because we have to create examples that show every type of subtype that a property might be, and remember to keep it up to date.
Has anyone implemented a better approach, maybe one that at least chased down into sealed classes in the same way as all the values of enums are specified, or used a different (better) schema library?
We’re using Jackson if it helps.
Thanks