Skip to content

Add ubiquitously-called internal functions to NAMESPACE #728

Add ubiquitously-called internal functions to NAMESPACE

Add ubiquitously-called internal functions to NAMESPACE #728

Triggered via pull request August 2, 2023 20:46
Status Success
Total duration 3m 8s
Artifacts

check-all-examples.yaml

on: pull_request
check-all-examples
2m 56s
check-all-examples
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
check-all-examples: <text>#L1
file=<text>,line=1,col=2,[absolute_path_linter] Do not use absolute paths.
check-all-examples: <text>#L1
file=<text>,line=1,col=1,[any_duplicated_linter] anyDuplicated(x, ...) > 0 is better than any(duplicated(x), ...).
check-all-examples: <text>#L1
file=<text>,line=1,col=1,[any_duplicated_linter] anyDuplicated(x) == 0L is better than length(unique(x)) == length(x).
check-all-examples: <text>#L1
file=<text>,line=1,col=1,[any_is_na_linter] anyNA(x) is better than any(is.na(x)).
check-all-examples: <text>#L1
file=<text>,line=1,col=1,[any_is_na_linter] anyNA(x) is better than any(is.na(x)).
check-all-examples: <text>#L1
file=<text>,line=1,col=3,[assignment_linter] Use <-, not =, for assignment.
check-all-examples: <text>#L1
file=<text>,line=1,col=3,[assignment_linter] Use <-, not ->, for assignment.
check-all-examples: <text>#L2
file=<text>,line=2,col=3,[assignment_linter] ->> can have hard-to-predict behavior; prefer assigning to a specific environment instead (with assign() or <-).
check-all-examples: <text>#L1
file=<text>,line=1,col=3,[assignment_linter] Avoid the assignment pipe %<>%; prefer using <- and %>% separately.
check-all-examples: <text>#L1
file=<text>,line=1,col=3,[assignment_linter] <<- can have hard-to-predict behavior; prefer assigning to a specific environment instead (with assign() or <-).