To avoid me being really annoying in PRs, would be good to have code styling and checks using pre-commit. As @hannahker has noted, we can use {lintr} to lint the code and force manual edits to match the style prior to committing. We could even use {styler} to automatically adjust the code, but would need some manual edits to the system. For instance, when testing it was messing with {box} to change box::use(a/b/c) to box::use(a / b / c).
To avoid me being really annoying in PRs, would be good to have code styling and checks using
pre-commit
. As @hannahker has noted, we can use{lintr}
to lint the code and force manual edits to match the style prior to committing. We could even use{styler}
to automatically adjust the code, but would need some manual edits to the system. For instance, when testing it was messing with{box}
to changebox::use(a/b/c)
tobox::use(a / b / c)
.I propose that we use the tidyverse style guide. https://style.tidyverse.org/index.html