Skip to content

Refine TransactionalOperator.executeAndAwait nullability #29919

Closed
@sdeleuze

Description

@sdeleuze

As pointed out in 09c64ae#r881209396, currently TransactionalOperator.executeAndAwait has 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.

Metadata

Metadata

Assignees

Labels

in: dataIssues in data modules (jdbc, orm, oxm, tx)theme: kotlinAn issue related to Kotlin supporttype: enhancementA general enhancement

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions