-
Notifications
You must be signed in to change notification settings - Fork 59
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
First stab at req_perform_sequential() #361
Conversation
Looks good to me. We need to think about error handling. It should probably be the same as in |
Yeah, I'll have a go at #310. I think an enum is the way forward. I've written up https://design.tidyverse.org/boolean-strategies.html to hopefully help me avoid this problem again in the future. |
#Conflicts: # NEWS.md # R/resp-status.R
#' | ||
#' @inheritParams req_perform_parallel | ||
#' @inheritParams req_perform_iteratively | ||
#' @param on_error What should happen if one of the requests throws an |
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.
@mgirlich let me know what you think of this error handling, and if it looks good, I'll port to req_perform_parallel()
.
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.
And req_perform_iterative()
, although that won't have the "continue"
option.
#Conflicts: # NEWS.md
Co-authored-by: Maximilian Girlich <maximilian.girlich@metoda.com>
Fixes #303. Fixes #310
@mgirlich this is just a quick proof of concept. If you think it looks good, I'll finish off the docs and tests. I did try allowing a
NULL
req
inreq_perform_iteratively()
, but it ended up feeling very artificial since thenext_req()
callback would then ignore both its arguments.If we have
req_perform_parallel()
,req_perform_sequential()
, then I think the matching name would bereq_perform_iterative()
, not iteratively.