Frédéric Nieto

an elegant way to get around that is to use associated consts in this way: ```rust pub trait PartialBox { const ID: BoxType; } impl PartialBox for MvhdBox { const...

Hi, I had the same need, and went increasingly frustrated with this library's syntax and maintainability of code so i made [Ktor-OpenAPI-Generator](https://github.com/papsign/Ktor-OpenAPI-Generator). We use it in production at our company...

There isn't such a feature. In theory it would't be too complicated to add an annotation to condition spec generation.

https://github.com/papsign/Ktor-OpenAPI-Generator/blob/8e207b4d700c361fee7fbc490f6c1def47798e60/src/main/kotlin/com/papsign/ktor/openapigen/route/OpenAPIRoute.kt#L47 this is the relevant logic to be eliminated i believe, however there may be side effects if the relevant modules use this for initialization. Maybe a per-module logic may...

The approach I would have taken is to just take a string and convert it based on `type`, this would allow for objects as json examples without additional effort.

@JavierPAYTEF What do you think about that, but a purely string based annotation that parses the content as json (or other based on a secondary optional property) ?

There is no way to handle multiple types of primitives in annotations in a cleaner way than you did. The cleanest is really to use a string with intellij `@Language`...

I don't know if an exhaustive guide about annotations exist, i just learned how to use them by fiddling around with them, and looking at annotation-heavy projects like spring.

the obvious way to do it if you are willing to do a one liner is to do something like this, with `params.param` as a nullable type: `val param =...

If you want to do a pr to add it i would accept it :)