`@Valid` on method parameter does not apply validation in 1.1.2

[koenpunt]

To raise a bit more awareness of a comment I placed on a specific commit.

4c3e75a#commitcomment-102568551

In 1.1.2 parameter validation was changed to somehow also support the @Validated annotation on individual arguments. This, however, did break validation with the @Valid annotation for us.

To elaborate a bit on our scenario; we use spring-graphql with kotlin and coroutines, and have input objects with nested @Valid annotations.

[rstoyanchev]

Can you provide something more specific to reproduce the scenario?

[koenpunt]

I've created a sample application with some of the type definitions of our application, with spring-graphql pinned to 1.1.1. When you run the playground and perform the following mutation you'll see validation errors in the application log:

mutation {
  createCustomerDetails(input:{
    email:"",
    name:"",
    phoneNumber:"",
    locale:"",
    deliveryDetails: null
  }) {
    id
  }
}

When you remove the override for the 1.1.1 version from the build.gradle.kt file, and rely on 1.1.2 provided through the boot started no validation errors are logged, and the application errors on the TODO(..) statement.

[rstoyanchev]

Thanks for the sample, I see the problem.

[rstoyanchev]

This should be fixed now in 1.1.3 snapshots.