OpenAPI, multipart and `:request`

[opqdonut]

@dzhus writes

I wonder if there's a way to use this form (:request) to specify an equivalent of what one can currently do with {:parameters {:multipart?

It appears that {:schema is only picked up by request body coercion.

(and the old form with {:parameters {:multipart .. :body ..} specified results in a OpenAPI spec missing the description for application/json content-type and associated request body schema – I'm trying to have the two content-types supported under the same endpoint, with accurate schemas communicated per each content type)

There are two issues here:

1. multipart-middleware doesn't know to look under :request. Should be straightforward to make it look there.
2. OpenAPI generation doesn't do what's expected when it encounters :parameters {:multipart .. :body ..}. I'll have a look at if this is fixable.

[opqdonut]

@dzhus did you use coercion? Did it work with {:parameters {:multipart ... :body ...}}? The OpenAPI generation was easy to fix, but it seems the coercion always wants multipart params to be present (understandably).