Juha Kukkonen

> > But if that comforts at all this could be done in not too distant future. :) > > Thanks, that would be great! :) IMHO it's quite an...

@oliver-impero Unfortunately not at the moment, I haven't fully set it up, My original goal was to have the github sponsors up and runnig but haven't finalized the setup. I...

Getting back to this I tried this out with editor.swagger.io only to find out that Swagger UI is unable to render OpenAPI version greater than `3.0.x`. So `3.1.x` is not...

Yes this is something that need to be addressed, Currently the implementation is quite spread out. I suggest that this would be postponed for sort time. Since the axum integration...

I'm now working on refactoring the extension related types to use one argument type and resolving logic across the extensions. With further PR:s we could get rid of this type...

Yes, the project cannot be "run" with `--all-features` flag set. All `*_extras` features are exclusive to each other and contains clashing implementations. This is alright since no-one should have both...

In order to support `--all-features` there is a need to seprate all extensions to own modules and create a new library for which is global for all extensions. This is...

True, `Any` as a response body or request body does nothing at the moment. It only works in `value_type`. Probably the support could be enhanced

@kellpossible With this I'm thinking should we ignore the type specific parsing implementation which is used for response body and request body and some other thing if not mistaken. And...

Yikes, this is not taken into account that objects could have reference to itself. Support for this could be added for sure.