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
{{ message }}
Repository navigation
Package cli use of "Suggests" rather than "Imports" seems odd #810
Yea, had this too, but I would only add rlang to Imports, not any of the others packages to keep the dependencies as few as possible. A solution for the other pkgs is to call rlang::check_is_installed() in cli functions you’re using other deps in.
Right. rlang is an optional dependency of cli, and it is only needed for some features, namely cli_abort() and co. Other packaging systems, e.g. Rust crates, have ways to express this, but unfortunately the R package system does not.
I cannot currently add rlang as a hard dependency because pak uses cli, but pak does not work with rlang. I can try to document better that you'll also need to import rlang if you use cli_abort().
Do you see any other way to improve the situation? Maybe cli_abort() could check that the called package depends on rlang, but that could be overkill and/or fragile.
Clearly
rlangfunctions are being used:cli/R/rlang.R
Line 46 in 3dd94c0
I encountered this when my package which just began importing
clifailed CRAN checks.