-
Notifications
You must be signed in to change notification settings - Fork 129
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
dry-run option for clean()
#1014
Comments
Something like it, sure. |
Hmm... the word "cleanable" does not actually get at the idea, and
Any sound good to you? Got a better idea for a name? |
Let's go with |
I am used to I even thought if this might server as a default to prevent undesirable events of people deleting important things - but I vaguely remember there is another option to undo cache cleaning, isn't it? |
Yes, to undo What other tools support |
Some shell and python tools AFAIR. Not sure if I've seen this in R before.
Totally understandable! I am totally fine with an extra function for it. |
Prework
drake
's code of conduct.Description
Would it makes sense to have a
dry_run
argument toclean()
to be able to check which targets will be removed from the cache? Especially when usingtidyselect
helpers it is unclear which targets will be affected.The text was updated successfully, but these errors were encountered: