-
Notifications
You must be signed in to change notification settings - Fork 290
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Map
service combinator
#435
Conversation
Signed-off-by: Lucio Franco <luciofranco14@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about calling this map_request
instead? I assumed map
would behave more like Future::map
, and mutate the response. It seems like we might want to have separate map_request
and map_response
combinators, so it could be good to disambiguate them.
Sorry for bikeshedding.
@hawkw I like that, will make the change and add the other one. 👍 |
This also closes #272 I believe? |
Approving subject to @hawkw's request and the one comment I made about the test :) |
Co-Authored-By: David Barsky <me@davidbarsky.com>
Signed-off-by: Lucio Franco <luciofranco14@gmail.com>
@davidbarsky they are both |
Signed-off-by: Lucio Franco <luciofranco14@gmail.com>
Signed-off-by: Lucio Franco <luciofranco14@gmail.com>
Signed-off-by: Lucio Franco <luciofranco14@gmail.com>
Co-Authored-By: David Barsky <me@davidbarsky.com>
Co-Authored-By: David Barsky <me@davidbarsky.com>
Co-Authored-By: David Barsky <me@davidbarsky.com>
Signed-off-by: Lucio Franco luciofranco14@gmail.com