Closed sigmafelix closed 9 months ago
@sigmafelix we can always make our own lints for naming. If you are able to come up with a clear naming convention that fits the default linters, then great. Otherwise, we can create a style. For example, the cf-naming conventions have a defined style that results in long variable or function names
@Spatiotemporal-Exposures-and-Toxicology Yes we can keep our own lints in this repo, but not sure if ROpenSci review system will accept user-defined linting rules. The function names are mostly changed for shorter names and function organization. Will make a PR for the changes soon.
Some functions,
distribute_*
in particular, give lint errors of variable names no longer than 30 characters. As rOpenSci requires a submission to pass lint checks, abbreviation of these function names is necessary. Naming conventions to consider are:{object type}_{function name}
as seen insf
functions (st_*
) orstringi
functions (stri_*
)terra
(e.g.,vect
,rast
, etc.){function group}_{function name}_{specific use case}
: currently used, but will get shorter group and function namesPerhaps
distribute_*
are too verbose, so I am thinking of usingpar
to represent parallelization (asparallel
functions'par*
naming).