Adapt to Reactor 3.8 JSpecify annotations #35501
Draft
+50
−32
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Dariusz Jędrzejczyk <[email protected]>
spring-projects-issues
added
the
status: waiting-for-triage
sdeleuze
added
type: task
chemicL
commented
Sep 18, 2025
| return adapter.fromPublisher(Flux.from(Mono.fromFuture(cachedFuture)) | ||
| .switchIfEmpty(Flux.defer(() -> (Flux) evaluate(null, invoker, method, contexts))) | ||
| .flatMap(v -> evaluate(valueToFlux(v, contexts), invoker, method, contexts)) | ||
| .switchIfEmpty(Flux.defer(() -> (Flux) Objects.requireNonNull(evaluate(null, invoker, method, contexts)))) |
There was a problem hiding this comment.
For code on the hot path, in reactor-core, I used assertions to silence the warnings where I knew nullable API is not returning a null value. I wasn't sure what strategy you'd like to take so I left a TODO somewhere near requireNonNull to address this.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
reactor-core 3.8.0-SNAPSHOT includes the migration from JSR-305-based nullability annotations to JSpecify.
This change adapts the spring-framework codebase to the changes caused by better nullability markers.
@sdeleuze please review and if something needs to change on the reactor-core side, I'd be happy to incorporate those recommendations.