I have been a fan of the idea of personal R packages for a while, but it always seemed like A Project That I Should Do Someday and someday never came. Because of the nature of iterative development, it often happens that I reuse the functions many times, mostly through the shameful method of copying the functions into the project directory. #' A detailed description of what the function does.As I have worked on various projects at Etsy, I have accumulated a suite of functions that help me quickly produce tables and charts that I find useful. #' A very brief description of what your function does We want to write specially formatted comments for it, i.e. the #' comments, so that roxygen2 can automatically build the documentation pages. Let’s say you have a script called my_function.R. Each function should be in its own separate file. It’s likely that you already have functions that you want to create a package for. Step 3: Add functions and write documentation I found this guide to be a helpful start if you want to learn more about software licenses. Note: The GPL-3 license seems to be a commonly recommended license for R packages. Suggests: knitr # optional packages that aren't strictly neededĭescription: What the package does, with more detail. Imports: dplyr # packages you need for the package, aka dependencies Version: 0.1.0 # see Jeff Leek's versioning convention

Title: What the Package Does # One line only, Title Case, and no period Below is an example (you will have to remove the “# comments” in your actual DESCRIPTION file). The DESCRIPTION file basically contains some information about the package.

You can do this in RStudio or with your favorite text editor.

Create r package rstudio