-
Notifications
You must be signed in to change notification settings - Fork 4
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
Other patterns for finding required packages #1
Comments
Yes, that's right. I also considered parsing DESCRIPTION. I adjust the function as soon as I find some time. But I won't be sorry, when someone is quicker. :-) |
Might be nice to also look for rstudio add-ins. |
The problem with most add-ins is, that you have no library() etc. call for them in any source files. Those they are hard to spot. |
ok @calligross I guess you wish it was easier. Nevermind, your tool is already very handy! Thanks. |
As a workaround: add for each add-in a |
smart, will try to stick to this rule |
This is great! I suggest, in addition to looking for packages that are called via
library(packagename)
,you also look for:
require(packagename)
packagename::function
import::from("packagename", ...)
The text was updated successfully, but these errors were encountered: