3.x: Use more appropriate operators when delegating to Flowable ops #6888
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.
Many
Single
andMaybe
operators delegate toFlowable
operators. This PR makes sure they use the most appropriate ones since there areSingle
- andMaybe
-specific operators onFlowable
for some time now.Some concatenating non-delayed Single operators now use the
Flowable.concatMapSingleDelayError(Functions.identity(), false)
because an array orIterable
ofSingle
s can't just throw anytime like aPublisher<Single<T>>
'sPublisher
could, hence a delay-error until boundary mode works the same but without the extra coordination of the more generalPublisher
variant.Resolves #6865
Completable
didn't have any delegation required changing.