Skip to content

rename map_future_with_context to map_future_with_request_data#1547

Merged
garypen merged 4 commits intomainfrom
garypen/1495-rename-mapper
Aug 19, 2022
Merged

rename map_future_with_context to map_future_with_request_data#1547
garypen merged 4 commits intomainfrom
garypen/1495-rename-mapper

Conversation

@garypen
Copy link
Contributor

@garypen garypen commented Aug 19, 2022

fixes: #1495

@garypen garypen requested a review from SimonSapin August 19, 2022 09:06
@garypen garypen self-assigned this Aug 19, 2022
Gary Pennington added 2 commits August 19, 2022 10:07
sigh...
For some reason, this test failed on windows in my PR build. I'm bumping
up the wait time to see if that makes it more predicatable.
@garypen garypen requested a review from SimonSapin August 19, 2022 11:19
@garypen garypen merged commit 50089db into main Aug 19, 2022
@garypen garypen deleted the garypen/1495-rename-mapper branch August 19, 2022 11:32
@Geal Geal mentioned this pull request Aug 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Consider renaming map_future_with_context

2 participants