Refine TransactionalOperator.executeAndAwait nullability
#29919
Assignees
Labels
in: data
Issues in data modules (jdbc, orm, oxm, tx)
theme: kotlin
An issue related to Kotlin support
type: enhancement
A general enhancement
Milestone
Comments
sdeleuze
added
in: data
sdeleuze
added a commit
to sdeleuze/spring-framework
that referenced
this issue
Feb 2, 2023
sdeleuze
added a commit
to sdeleuze/spring-framework
that referenced
this issue
Feb 2, 2023
Before this commit, TransactionalOperator.executeAndAwait had a rigid null-safety handling. This commit takes advantage of Kotlin capability to allow to deal with both non-null and nullable depending on the nullability of the lambda. Closes spring-projectsgh-29919
mdeinum
pushed a commit
to mdeinum/spring-framework
that referenced
this issue
Jun 29, 2023
Before this commit, TransactionalOperator.executeAndAwait had a rigid null-safety handling. This commit takes advantage of Kotlin capability to allow to deal with both non-null and nullable depending on the nullability of the lambda. Closes spring-projectsgh-29919
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As pointed out in 09c64ae#r881209396, currently
TransactionalOperator.executeAndAwaithas a rigid null-safety handling and hardcode non-null for the input parameter type and nullable for the return value.Kotlin allows to deal with both non-null and nullable depending on the nullability of the lambda, we should take advantage of that.
The text was updated successfully, but these errors were encountered: