The one-time (per package) functions are mostly those that set up a certain type of infrastructure for the package. Some of these functions you’ll only need to use once for a package. Set the package up to facilitate using Travis CI with the packageĬreate a file where you can add comments to include with your CRAN submission.Īdd a file to the package to give news on changes in new versions You’ll receive an email with a link to the results. Specify files that should be ignored when building the R package (for example, if you have a folder where you’re drafting a journal article about the package, you can include all related files in a folder that you set to be ignored during the package build)Ĭheck the full R package for any ERRORs, WARNINGs, or NOTEsīuild a version of the package for Windows and send it to be checked on a Windows machine. Set up the package to include a README file in R Markdown format Save an object in your R session as a dataset in the packageĪdd a package you’re using to the DESCRIPTION file Load the code for all functions in the packageĬreate \man documentation files and the “NAMESPACE” file from roxygen2 code Here are some of the key functions included in devtools and what they do, roughly in the order you are likely to use them as you develop an R package: FunctionĬreate the file structure for a new package
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |