Robbe Sneyders

@rjkooijman Happy to have this change in connexion, however I would move away from the `pass_operation_arg_name` and provide the operation under a fixed name. I'd like to do the same...

Hi @v-pap. If you're still willing to get this merged, could you: - Add a test for the behavior - Rebase on and target this PR to the `v2` branch

Hi @hauntsaninja, thanks for the PR. It seems like there was a [clarification](https://github.com/tedepstein/OpenAPI-Specification/blob/325db7f50610aed0af967d5907f9e5f6a32168a1/proposals/2019-10-31-Clarify-Nullable.md#if-a-schema-specifies-nullable-true-and-enum-1-2-3-does-that-schema-allow-null-values-see-1900) to the OpenAPI spec last year that specifies that this behavior is not allowed though: > **If...

@Ruwann could you take a look at this?

Thanks for the report @aparcar. @dtkav do you have some time to look at the open PRs on the repo?

Dropping 2.x would be an issue for connexion @aparcar.

Thanks @fgreinacher! I've submitted a PR to fix the failing tests due to a new Flask version: https://github.com/spec-first/connexion/pull/1572. I'd like to merge that one first. Feel free to review it.

Sorry for the delay, I was on vacation myself :) Should be good to go now. I'll prep a release.

Thanks for the report @psauxgrep. Can reproduce.

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