I've suggested adding a README.Rmd file, which compiles to README.md with knit("README.Rmd"). (See ?devtools::use_readme_rmd). This has two advantages:
Code is compiled without >, which makes it a bit easier to copy/paste into a terminal.
This keeps the README up to date with the package usage and output (for example, in this process I found the README uses dust_colnames, which appears to have been renamed sprinkle_colnames in the released version).
I also added a .Rproj file just so that developers can immediately clone and open the project, but it's up to you whether to use it.
I've suggested adding a README.Rmd file, which compiles to README.md with
knit("README.Rmd")
. (See?devtools::use_readme_rmd
). This has two advantages:>
, which makes it a bit easier to copy/paste into a terminal.dust_colnames
, which appears to have been renamedsprinkle_colnames
in the released version).I also added a .Rproj file just so that developers can immediately clone and open the project, but it's up to you whether to use it.
Thanks for your awesome work on this package.