Juha Kukkonen

I have thought this too. Just haven't implemented it yet since this indeed is not walk in a park. :D For example in actix-web you can have return type such...

> > Another thing that would be easier to implement though is to actually implement strictier rules for defining responses. Like > > if function would have any response I...

Yeah they are not supported. The reason is that there is no good way to serialize them as OpenAPI doc and the only way to represent tuples are to represent...

Yeah, we could, and also what we can do also is to implement support for this behaviour similary already existin for UnnamedStruct in https://github.com/juhaku/utoipa/blob/master/utoipa-gen/src/schema/component.rs#L323. So what it does it creates...

Yes `flatten` is not supported at least yet. To support this there is actually couple of things could be done and there is no need to have `#[component(nested = true)]`...

Yeah that syntax is the new syntax coming in version 2.0.0 once released. In 1.1.0 release the syntax is bit more complicated similar to the existing for tide and warp...

Response body and request body is resolved in elsewhere thus not supporting path expression. This needs a change to current implementation. I'll note this to the project's kanban board as...

Hi, unfortunately this is not supported at the moment. Although implementing support for this is somewhat simple. For example I could implement following syntax where `ref(...)` would translate above mentioned...

Yes that is not actually bug but unimplemented by desing. Since OpenAPI 3.0 version does not have `description` or `summary` in fields which are references to another components. See here...

> Hm, that's very unfortunate. Would it be possible to enable it via a feature flag, like `openapi-3.1-preview`? That would be great :) Yes, it could be added, only thing...