Fix onErrorContinue consumer nullability - #4324
Open
arnabnandy7 wants to merge 1 commit into
Open
arnabnandy7 wants to merge 1 commit into
arnabnandy7 wants to merge 1 commit into
Conversation
Signed-off-by: Arnab Nandy <arnab_nandy7@yahoo.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Kotlin consumers of
Flux#onErrorContinueandMono#onErrorContinuenow correctly infer that the value associated with an error can be nullable.Annotate the second
BiConsumertype argument with JSpecify's@Nullableacross allonErrorContinueoverloads and the internalOnNextFailureStrategy. This aligns the public nullability contract with existing behavior when an error has no associated upstream value. The Javadocs now explicitly document this case.Fixes #4285.