box
box copied to clipboard
klmr
Write reusable, composable and modular R code
Things like * [ ] ‘roxygen2’ documentation * [ ] support for testing * [ ] support for FFI * [ ] module implementation details * [ ] imports (lack...
Would be probably required before supporting #23, upgrades, I guess. It would be great to support semantic versioning. (Btw. it would also be great to have versioned dependencies, but I...
Currently **box** does not render Markdown markup in the documentation, which would be very convenient. It seems to be hackable though with: ```r use::box(m = a/module) old
### Error description I'm test-driving **box** (1.1.0) currently, and I'm pretty happy with it so far (thanks!). I have developed a module and try to document the functions in the...
As discussed in #262, there should be a suite of benchmarks of different operations, and how they compare to equivalent base R operations. The results should be published as a...
Currently loading a module that isn’t already in cache parses and evaluates all its source files, which is potentially time-consuming, especially when compared to loading a package: installed R packages...
### Error description ``` > shinytest::recordTest() Error in sd_startShiny(self, private, path, seed, loadTimeout, shinyOptions) : Error starting application: Loading required package: shiny Warning: package 'shiny' was built under R version...
While developing interactively, it would be fantastic if the modules are re-loaded automatically in the background every time a module has changed. This is how the [`%autoreload`](https://ipython.org/ipython-doc/3/config/extensions/autoreload.html) magic works in...
When interactively developing a script, it’s common to go back and modify, then rerun, a `box::use` top-level declaration. Currently, this causes attached environments and aliases to accumulate. To illustrate, consider...
Currently modules’ `script_path` is aware of `Rscript` and `R CMD BATCH` but not littler (except maybe incidentally). Ensure that it works.