Elio Campitelli2d ago

I developed an #RStats package to get data from a remote service. Functions allow caching results, so that they will just return the saved files if the request is the same. I tend to be conservative and set the cache option to FALSE by default, but now I'm wondering if it would be more user friendly (and friendlier to the remote API) to set the default to TRUE.

What say the R community?

Use cache by default
75%
Don't use cache by default
25%
Poll ended at .
Show threadAdam H. Sparks 2d ago
@eliocamp I use {httr2}’s caching by default in session. Between, I expect the user to save and reload the data if it’s necessary. https://codeberg.org/ropensci/read.abares/src/branch/main/R/retry_download.R
read.abares/R/retry_download.R at main

read.abares - Harvest data from Australian Bureau of Agricultural and Resource Economics and Sciences (ABARES) part of the Australian Department of Agriculture, Fisheries and Forestry and the Australian Bureau of Statistics (ABS) for your work in R

Codeberg.org
Show threadElio Campitelli1d ago
@adamhsparks Do you expect users to use the function to download the data to sow folder and then retrieve it via file paths in a different part of the code?
Show threadAdam H. Sparks 
@eliocamp it reformats the data most of the time. I’d expect you’d use {targets} if you really needed some sort of cache beyond what I offer.
Mar 21 at 5:16amWeb
Show threadAdam H. Sparks 1d ago
@eliocamp this was also part of the discussion during the review and the reviewers and I agreed on dropping it just due to complexity and like I said, {targets} exists.