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
Currently we handle deps through install_deps() only for CRAN packages, but people do use github versions of some packages, sometimes (all the time?). This is trickier to handle, and would require the user to be proactive about it, but it could be nice to be able to specify remotes as in a DESCRIPTION file. Would this be part of the config file? I guess it does ask the question of how we want to handle all config things: single file vs many separate, single-purpose files.
The text was updated successfully, but these errors were encountered:
I'd say single config file. I think multiple files will just add too much cognitive overhead. We could then use the list_deps() functionality to flag any packages used in the reports that are not listed in the config file.
Currently we handle deps through
install_deps()
only for CRAN packages, but people do use github versions of some packages, sometimes (all the time?). This is trickier to handle, and would require the user to be proactive about it, but it could be nice to be able to specify remotes as in a DESCRIPTION file. Would this be part of the config file? I guess it does ask the question of how we want to handle all config things: single file vs many separate, single-purpose files.The text was updated successfully, but these errors were encountered: