-
Notifications
You must be signed in to change notification settings - Fork 17
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
set curl options globally #48
Comments
@maelle can you give it a try when you get a chance? if so, install like note that the options set with these new functions are only picked up on function intialization, so if you set new options you have to remake the client object. let me know if that seems good or not. |
also @dirkschumacher and @mikkelkrogsholm - see above comment, any thoughts on how these functions are implemented? let me know if any questions/problems |
Does this mean an user could set the agent in their .Rprofile for instance and thus overrides all possible |
doesn't support using a file, but I did think about that. I looked around at other http clients and didn't see any examples of using a file. But doesn't mean we can't do it. I do worry a bit about users setting these things in a file and then forgetting about them, and then wondering what's going wrong later on. I guess one could simply give a message or so reminding the user that they are using options from a file. |
* add ropensci footer to readme * #48 added set_* fxns - working with httpclient and httprequest and thus async/asyncvaried
main use case is when using
crul
inside a package, becomes esp. important when e.g., a pkgfoo
usescrul
, then another pkgbar
usesfoo
, which makes likelihood of arg. collisions more likelyThe text was updated successfully, but these errors were encountered: