Follow up to #1979 to avoid retryWhen ambiguity #2079
Merged
Conversation
This file contains 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
bsideup
reviewed
Mar 19, 2020
| * @return the actual companion to use, which might delay or limit retry attempts | ||
| */ | ||
| Publisher<?> generateCompanion(Flux<RetrySignal> retrySignalCompanion); | ||
| public abstract Publisher<?> generateCompanion(Flux<RetrySignal> retrySignals); |
There was a problem hiding this comment.
in an abstract class, you may want to have a final method that wraps the user-provided one, so that we keep some control. Usually it makes it easier to make changes in future
bsideup
reviewed
Mar 19, 2020
bsideup
approved these changes
Mar 19, 2020
rstoyanchev
reviewed
Mar 19, 2020
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.
TODO: marble diagrams for the various
Retryfactories