Give advice about good practices when building R packages. Advice includes functions and syntax to avoid, package structure, code complexity, code formatting, etc.
Version: | 1.0.2 |
Imports: | clisymbols, covr, crayon, cyclocomp (≥ 1.1.0), desc, jsonlite, lintr, praise, rcmdcheck, rstudioapi, tools, utils, whoami, withr, xml2, xmlparsedata (≥ 1.0.1) |
Suggests: | testthat, knitr, rmarkdown |
Published: | 2018-05-02 |
Author: | Gabor Csardi [aut], Hannah Frick [aut, cre] |
Maintainer: | Hannah Frick <hfrick at mango-solutions.com> |
BugReports: | https://github.com/mangothecat/goodpractice/issues |
License: | MIT + file LICENSE |
URL: | https://github.com/mangothecat/goodpractice |
NeedsCompilation: | no |
Materials: | README NEWS |
CRAN checks: | goodpractice results |
Reference manual: | goodpractice.pdf |
Vignettes: |
Custom Checks goodpractice |
Package source: | goodpractice_1.0.2.tar.gz |
Windows binaries: | r-devel: goodpractice_1.0.2.zip, r-release: goodpractice_1.0.2.zip, r-oldrel: goodpractice_1.0.2.zip |
macOS binaries: | r-release: goodpractice_1.0.2.tgz, r-oldrel: goodpractice_1.0.2.tgz |
Reverse suggests: | taxlist |
Please use the canonical form https://CRAN.R-project.org/package=goodpractice to link to this page.