Robbe Sneyders

Hi @MarcoRizk, thanks for the PR. There is currently indeed a limitation in Connexion when using multiple content types, but I don't think this is sufficient to solve it. I...

Hi @sisp, This is a known issue (see #1409, #1263, #1300, #1013, #1231) and is caused by some custom validation code. I'd like to tackle this as part of the...

The OpenAPI spec defines [serialization formats](https://swagger.io/docs/specification/serialization/) for arrays in the query string. `?ids[0]=1&ids[1]=2` does not seem to be supported. `?ids[]=1&ids[]=2` seems to be the default with a parameter name of...

Hi @robertoberto Looks neat. I don't think we should include it in connexion since the file structure of an API is quite opinion based, but I would be open to...

[editor.swagger.io](https://editor.swagger.io/) also contains a boilerplate generator for Connexion #446. We should add it to the ecosystem section as well.

Thanks @m-nikhil. Could you rebase on and target this to the `v2` branch? We'll cherrypick it to main for v3 later.

Thanks @m-nikhil Two remarks: - This PR doesn't actually fix #655 since that one is about incoming content-types, not response types. It should fix #1500 though. Could you update the...

Thanks for the report and detailed info @LutzVenhofen. This is currently indeed not supported in Connexion, but any work on it would be appreciated.

Closing in favor of #1569.

#1588 and #1591 tackle this for request and response validation respectively.