This repository has been archived by the owner on Jan 27, 2023. It is now read-only.
support registration for client that mixes rx and non-rx return types #19
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Currently when constructing a client using FlowableClientMethodInvoker, calls fail for any non-Rx types due to an NPE caused by the below lines, since converters are only registered for Rx classes:
Function<Flowable, ?> converter = converters.get(responseType.getRawType());return converter.apply(flowable);Implement short-circuiting of any non-rx method invocations to allow both Rx and non-Rx return types to be registered on the same client.