3.x: Fix method argument naming across types #6853
Merged
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.
Make method argument naming consistent between the base reactive classes, adjust some of the naming for all.
In addition, the null-check was missing from
blockingMostRecent
.Resolves #6832
The utility program has to be run manually to list the inconsistencies. The remaining inconsistency is due to
merge
because its argument issources
forFlowable
/Observable
butsource
forSingle
/Maybe
nested.