You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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
changed the title
1.1.2 breaks parameter validation with @Valid annotation@Valid on method parameter does not apply validation in 1.1.2
Mar 6, 2023
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.The text was updated successfully, but these errors were encountered: