All current code needs to be reformatted to follow the Tidyverse Style Guide.
This will allow for cleaner code and use of the linter + styling.
STEPS TO REPRODUCE
Run the linter in R Studio
You will see issues with the code and recommendations to use .data$
We don't want to always use .data$ but rather follow the Tidyverse style guide
IMPACT
Annoying bug that will only accumulate more issues if not fixed with small amount of code present.
ADDITIONAL
Look at acceptable code for loops, spacing, embracing, etc.
Documentation should follow guide when discussing packages
importFrom may be helpful
Should add NEWS.md at this point in development
Follow Git commit messages recommendations
Change helpers to follow error messages style. Uses cli::cli_abort()
An error message should start with a general statement of the problem then give a concise description of what went wrong. Consistent use of punctuation and formatting makes errors easier to parse.
BUG DESCRIPTION
All current code needs to be reformatted to follow the Tidyverse Style Guide. This will allow for cleaner code and use of the linter + styling.
STEPS TO REPRODUCE
.data$.data$but rather follow the Tidyverse style guideIMPACT
Annoying bug that will only accumulate more issues if not fixed with small amount of code present.
ADDITIONAL
importFrommay be helpfulNEWS.mdat this point in developmentcli::cli_abort().data$may be resolved withselect(all_of(var)). See tidyverse blog post