Open gavinsimpson opened 5 months ago
Thanks again for this @gavinsimpson.
@gmyenni - I agree with this suggestion and would be happy with either adding an explicit argument or the ...
approach. Let me know if you want to chat details. We should probably also bump the default timeout again.
When running
load_rodent_data(my_path)
I encountered an error (cause unknown - though I presume it was due to a timeout) that caused the function to fail. I then randownload_observations(my_path)
and I got:Increasing
timeout
worked fine and the data were download tomy_path/PortalData
. It would be helpful to allowtimeout
to be passed fromload_rodent_data()
>load_datafile()
>download_observations()
, either by addingtimeout
as an argument to the various functions in the stack or by allowing...
on the functions that call (or cause to be called)download_observations()
. The...
mechanism would be preferable, I think, but it does bring with it the issue of it causing misspelled argument names to be silently ignored unless you go to a little more effort and actually check the...
and ensure that all passed arguments are used (e.g. usingrlang::check_dots_used()
: https://design.tidyverse.org/dots-inspect.html (Note that at that link it's talking about S3 methods, but the principle applies generally.)Ideally I'd like to be able to use
load_rodent_data(my_path, timeout = 360)
and have that value be passed along, so I can follow @ha0ye's nice vignette without having to deviate from the code due to github, limiters/timeouts, etc.The error I got with
load_rodent_data(my_path)
was