devtools
devtools copied to clipboard
r-lib
Tools to make an R developer's life easier
This requires more analysis, but my current thinking is that `install()` should not, by default, be so eager to update packages.
I am experiencing an issue similar to this one: https://github.com/r-lib/devtools/issues/179 I am developing a package using devetools::load_all() to test things. I am using eval within a tryCatch environment. Part of...
This uses `use_tidy_dependencies()`, which most consequentially adds glue to Imports, and adds brings in `import-standalone-purrr.R` To start to make use of these I've replaced most instances of `paste0()` with `glue()`....
I have some invalid tex code in a manual (that I'm still trying to track down the exact error). When I tried to run `build_manual()`, it gives an error: ```r...
Inspired by revising the vignettes chapter of R Packages. One thing that has come into focus is that we want to discourage the keeping of built vignettes inside a source...
The `show_news()` function is hard-coded to check only for `NEWS` in a package directory: https://github.com/r-lib/devtools/blob/7cc2bdf74cbae90233fa6c84f221631d1876598d/R/show-news.R#L10 However (from the docs of `utils::news()`): >[...] it is attempted to read its news in...
And remove any advice that conflicts with `use_release_issue()`
https://mac.r-project.org/macbuilder/submit.html supports checking on either (i) R release or (ii) R development. It's been there for at least a month now.
`devtools::build_rmd()` is supposed to be a generic function to build any rmd Currently it will error on some format like `rmardown::pdf_document()` (which could be used in vignettes too) because of...
