Robbe Sneyders

Yes indeed @gaurav-triverus `g` is only available within the context of the Flask application. Since Connexion 3's security functionality is performed by middleware wrapped around the Flask application, it's not...

Hi @alfechner, I think you have two options: - Use a different content type like `multipart/form-data` instead. ```yaml requestBody: content: multipart/form-data: schema: type: object properties: file: type: string format: binary...

Ok, thanks for diving into this and reporting back. Any reason you're creating a new request instead of importing the one we make available via `from connexion import request`?

Is the `infinite loop` issue you mention the same as described in https://github.com/spec-first/connexion/issues/1812?

Thanks @chbndrhnns, Not sure if this is inconsistent. If you change your example spec to (note the trailing slash after `hello`): ```yaml "paths": { "/hello/": { "get": { ``` You...

Thanks for the detailed issue @Gidgidonihah Inferring the content type correctly in all cases is not straightforward, especially due to the difference in response definition between the Swagger 2 and...

Thanks @etvahala! 2 points: - The [openapi docs](https://swagger.io/docs/specification/authentication/#scopes) only describes scopes for `oauth2` and `OpenID` security schemes, and mentions the scopes are empty for all other schemes. https://github.com/OAI/OpenAPI-Specification/issues/1366 seems to...

Ping @etvahala @Ruwann

Thanks @etvahala! I don't think the line you linked is relevant, but the next one is: > For other security scheme types, the array MAY contain a list of role...

Hi @Elthas17, To run connexion, you need to target the connexion app (`connexion_flask_app` in your code). To run flask-migrate, you need to target the flask app (`app` or `connexion_flask_app.app` in...