-
Notifications
You must be signed in to change notification settings - Fork 8
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
properly import non-exported functions. #3
Comments
Above method will not work. Associated -> include copies of functions. ensure proper acknowledgement and license inclusion. |
Still need to address:
|
in
In the future such functions might be exported by another package (if I followed correctly 👼 ) cf e.g comment by @jennybc in this closed issue r-lib/usethis#126 (comment) |
Definitely get in touch about usethis functions that you wish were exported. We just exported a few more, for example, based on feedback: r-lib/usethis@979a865 |
Oh yeyy!
Here's the checks output:
I did the same as @maelle for the whole This is a lot I know. Perhaps I could take a stab at some roxygen documentation if you'd consider exporting any of the above? I also wonder if in future, some might make sense as standalone lightweight packages of their own. eg I could see the styling functions as a useful and sensible collection. Also some functions for checking or working with project/package metadata might also make sense together. |
Checks note (and SO discussion shows) that
:::
function calling within packages is not permitted on CRAN.To import correctly, Include details in roxygen function documentation, following
convention and remove
:::
notation in functions.The text was updated successfully, but these errors were encountered: