Jean-Marc Le Roux

Bon... c'est un joyeux b***el niveau traçabilité donc. Ca confirme mon intuition de faire un "hash" qui représente la modification apportée par le texte, pour pouvoir comparer les articles en...

> Typically the new type pattern is a struct with one unnamed field e.g. struct Foo(Bar); And that is supported, but struct with named fields is not considered as a...

I can confirm I have the exact same problem. In addition to `example` I also tried `content_type` (cf #660). But the same problem occurs. Only `status` works.

I thought I could workaround this by using a newtype: ```rust struct Relationship { data: T, links: RelationshipLinks, } #[derive(ToSchema)] struct BufferResourceRelationshipToOne( #[schema(inline)] Relationship, ); #[derive(ToSchema)] struct BufferResourceRelationshipToMany( #[schema(inline)] Relationship,...

> could we update ToSchema::schema() to take the actual generic type(s) (schema(s)) as an optional argument? Something like: ```rust trait ToSchema { fn schema(params: Option) -> ( &'static str, RefOr,...

Using `cargo expand` I found that the code generated by `#[derive(IntoResponses)]` is along the lines of: ```rust impl utoipa::IntoResponses for MeshResourceResponse { fn responses() -> std::collections::BTreeMap< String, utoipa::openapi::RefOr, > {...

As a workaround, implementing `::actix_web::Responder` for my generated response types does the job: ```rust impl ::actix_web::Responder for #response_ident { type Body = ::actix_web::body::BoxBody; fn respond_to(self, _req: &::actix_web::HttpRequest) -> ::actix_web::HttpResponse {...

@juhaku if that's still on the table I'll try to do it.

@juhaku @smndtrl PR: #963

@travi I have `conventional-changelog-conventionalcommits` installed and I still have the problem. ``` [4:05:29 PM] [semantic-release] › ℹ Running semantic-release version 21.0.2 (node:387) ExperimentalWarning: Importing JSON modules is an experimental feature...