You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If load_all() doesn't find a DESCRIPTION file in the package directory, it is created. As of #803, parent directories will not be scanned for a DESCRIPTION file. #816 explicitly documents and tests this behavior.
Now the behavior of load_all() is difficult to understand and communicate: If a directory happens to contain R, src or data, a DESCRIPTION is created -- if not (and no DESCRIPTION exists), an error is thrown:
I suggest a new argument create_if_missing that governs this behavior. If TRUE, always create (perhaps via devtools::setup()). If FALSE, never create (but use the usual pkg <- as.package(pkg) idiom). If NULL (the default), the user will be asked if in interactive mode (otherwise same as FALSE).
This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/
lockbot
locked and limited conversation to collaborators
Sep 18, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If
load_all()
doesn't find aDESCRIPTION
file in the package directory, it is created. As of #803, parent directories will not be scanned for aDESCRIPTION
file. #816 explicitly documents and tests this behavior.Now the behavior of
load_all()
is difficult to understand and communicate: If a directory happens to containR
,src
ordata
, aDESCRIPTION
is created -- if not (and noDESCRIPTION
exists), an error is thrown:I suggest a new argument
create_if_missing
that governs this behavior. IfTRUE
, always create (perhaps viadevtools::setup()
). IfFALSE
, never create (but use the usualpkg <- as.package(pkg)
idiom). IfNULL
(the default), the user will be asked if in interactive mode (otherwise same asFALSE
).@hadley: Is this sufficient for the use case you described in your comment?
The text was updated successfully, but these errors were encountered: