Join 📚 James's Highlights
A batch of the best highlights from what Jimmy's read, .
Using roxygen2 is generally handy, starting with your no longer needing to edit the NAMESPACE by hand. If your package doesn’t use roxygen2 yet, you could use Rd2roxygen to convert the documentation.
Workflow automation tools for package developers
Maëlle Salmon
R CMD check or devtools::check\(\) will check your package for adherence to some standards (e.g., what folders can there be) and run the tests and examples. It’s a useful command to run even if your package isn’t intended to go on CRAN.
Workflow automation tools for package developers
Maëlle Salmon
* covr::package\_coverage\(\) calculates test coverage for your package. Having a good coverage also means R CMD check is more informative, since it means it’s testing your code. 😉 covr::package\_coverage\(\) can also provide you with the code coverage of the vignettes and examples!
Workflow automation tools for package developers
Maëlle Salmon
...catch up on these, and many more highlights
Readwise