-
hits_by_regex.R looked orphaned as it was the only batch of functions not documented roxygen style, plus it contained calls to libraries instead of import declarations. It doesn't seem heavily used, b…
-
AFAIK, there are currently no guidelines about this in the _tidyverse style guide_, but I was wondering if {styler} should adopt a convention to remove empty lines between roxygen documentation and th…
-
In the following we will use the following naming convention:
function names using camelCase notation
arguments, objects and class names using snake_case (underscore for separating)
In general, the 'd…
-
It combines lines incorrectly and adds unnecessary indentation:
```
#' @examplesIf megamation:::has_creds()
#' date
-
Create all the files to be able to move VMStools to cran.
-
As of 13-Aug-2013 we have decided to make `.Rd` files the primary documentation; only basic Roxygen material (parameter definitions?) will be kept in the R code. At some point we should go in and str…
-
A general Housekeeping Epic. here we can dump **overarching / meta tasks** related to:
- package structure
- CI/CD
- refactoring
- documentation
- testing
pr130 updated
3 years ago
-
I think that is standard to have a package_name-package.R file in the R folder of the package. This just contains some roxygen-style comments at the top which then get compiled to do various things ac…
-
Dear author(s),
my apologies if opening an issue is not appropriate for my request. I am facing a situation that has already been raised on stackoverflow, but no satisfying solution has been propos…
-
## Goal
Currently have to pull locally and run `pre-commit --all-files` and commit the result to apply autofixes, which can be slow and annoying especially in final stages of review with a number of …