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
In my workflow, I snapshot development dependencies into the lockfile using renv::snapshot(type = "explicit, dev = TRUE). Whenever I open the project, I get the message, that the project is out of sync. I think this is because renv::status() shows that there are several packages that are installed and recorded but not used, as expected.
When I run renv::status(dev = TRUE) , it correctly returns that the lockfile is up to date.
Would it be a possibility to make the default for the dev argument of renv::status() configurable, similar to what I can do with the settings for snapshot.type? This could prevent quite some confusion, as e.g. code reviewers or colleagues do not necessarily immediately know why the message is shown.
Reprex:
devtools::create("newpackage", open=TRUE)
renv::init(bare=TRUE)
renv::install("usethis", prompt=FALSE)
usethis::use_package("usethis", type="Suggests")
renv::snapshot(type="explicit", dev=TRUE, prompt=FALSE)
renv::status()
#> The following package(s) are in an inconsistent state:#> ...renv::status(dev=TRUE)
#> No issues found -- the project is in a consistent state.
Hey everyone,
In my workflow, I snapshot development dependencies into the lockfile using
renv::snapshot(type = "explicit, dev = TRUE)
. Whenever I open the project, I get the message, that the project is out of sync. I think this is becauserenv::status()
shows that there are several packages that are installed and recorded but not used, as expected.When I run
renv::status(dev = TRUE)
, it correctly returns that the lockfile is up to date.Would it be a possibility to make the default for the
dev
argument ofrenv::status()
configurable, similar to what I can do with the settings forsnapshot.type
? This could prevent quite some confusion, as e.g. code reviewers or colleagues do not necessarily immediately know why the message is shown.Reprex:
Maybe related to #1019
Thank for the consideration!
Martin
The text was updated successfully, but these errors were encountered: