feat: allow to make future chain request with ResponseFuture and ResponseStream #543
Conversation
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
savy-91
force-pushed
the
response-future
branch
from
7262070 to
56aac2c
Compare
savy-91
force-pushed
the
response-future
branch
from
56aac2c to
d3ad27e
Compare
savy-91
changed the title
Member
|
I think instead of adding support for chaining Let me know if that would solve all use cases. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Same as #419 but rebased on master.
Also adds
responseTransformto chain StreamTransformers to a ResponseStream.