Closed atusy closed 3 years ago
Hmmm, but you're not really deleting the pin; you're deleting the cached version.
Oh yeah, that is true... Thanks.
Maybe users can delete caches easily (see code below). So, I'll be back if I come up with better solution to be included by pins package.
pins::board_url() |>
pins::pin_download("https://example.com") |>
dirname() |>
unlink(recursive = TRUE)
Maybe something extending pins::cache_prune()
?
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue.
Currently,
pin_delete.pins_board_url
is not allowed, and raisesabort_board_read_only("board_url")
.However, I think there are some cases people want to remove them for sure to reduce the disk space.
I think we should add
force
argument which behaves like belowforce = FALSE
(default), abort and let user suggest to setforce = TRUE
explicitly.force = TRUE
, delete it.