I second @tyluRp - if you have functions that you will only use in one project, I would keep them organized in a
source/ folder (following "Good Enough Practices in Scientific Computing"):
| -- data/
| ---- data.csv
| -- docs/
| ---- notebook.Rmd
| -- source/
| ---- create_data.R
| ---- clean_logical.R
| -- project.Rproj
You can call these from the top of your
If you are going to use these same functions across projects, a package is a far better bet. We recently had an excellent thread on a very similar topic. Here are a couple of takeaways that were mentioned:
- While package development seems difficult, it does not have to be!
@jrlewi recommends using Git to track your package, and I would add that keeping it stored on GitHub is an excellent idea as well
- don't worry about complying with CRAN requirements at the outset, or about using things like unit testing, continuous integration, and code coverage
- I would, however, suggest that passing
devtools::check() without warnings or errors is a good metric for success
If you want something to look at for a bit of inspiration, I have a small package that I named after myself on GitHub. I have no intention of ever submitting it to CRAN, but I use to to store a few "general" functions that I find useful across many projects or tasks.
Some package development resources from the same thread as above:
And finally, make sure you have
roxygen2 installed! They're all very helpful for different facets of package development.