Closed potash closed 3 years ago
Unfortunately, the drake_cache()
function is too deeply embedded in other package functions to safely throw an error or even a warning. And the current behavior is consistent with drake
's original intention to be super flexible about where the cache is located. For a pipeline toolkit that is deliberately more strict and paternalistic about the cache location, consider switching to targets
, the long-term successor to drake
.
Prework
Description
Creating a
drake_cache
with a non-existant path returnsNULL
which if passed in turn tomake()
uses the current working directory.Reproducible example
Expected result
I think it would be reasonable to either raise an error or (try to) create the non-existent path.
Session info