-
Notifications
You must be signed in to change notification settings - Fork 321
Closed
Labels
status: duplicateA duplicate of another issueA duplicate of another issue
Description
Although it should be possible to validate any managed bean with Spring directly the following example doesn't seem to work in the current snapshot build.
@GraphQlController
@Validated
class Mutations {
@MutationMapping
fun mutate(
@Argument
@Valid
update: Update
): Result {
....
}
}
Where Update
contains validation constraint annotations such as
data class Update(
@field:Length(min = 2)
val name: String?
)
It seems currently an unvalidated data object is passed into the mutate
handler.
I haven't dug too deep yet but I think the root cause could be how the Update
object is instantiated and passed to the handler method. It could also be a missunderstanding of how this should be working on my end.
Is JSR-303 validation supported in the current snapshot?
Metadata
Metadata
Assignees
Labels
status: duplicateA duplicate of another issueA duplicate of another issue