avoiding lots of lintr warnings

[w-jan]

I'm a beginner using checklist, so perhaps my question is easy to answer. When checking the grammar in a commit with lintr, I get a lot of warnings like "no visible global function definition for '%>%'" or "no visible global function definition for 'bind_rows'," which are due to the lack of a specific reference to the package they originate from.
I can't find a way to get rid of these warnings on GitHub smoothly. By smoothly, I mean without having to specifically reference the package throughout the code.
How do you handle this? Thnx for reaching a hand !

[ThierryO]

I suppose you use bind_rows() in a function? Instead of loading the package at the top of the script, you should load the package inside the function. See the example below. Note that I use require() instead of library(). require() loads the package as library() does but it returns a TRUE or FALSE depending on R was able to load the package. Wrapping that instead of a stopifnot() ensures that your function errors when then package is not available.

An alternative is to use the package::function notation. E.g. dplyr::bind_rows().

my_fun <- function(x, y) {
  stopifnot(require("dplyr"))
  bind_rows(x, y)
}

In case of %>%, it is easier to replace it with the base pipe |>.

[w-jan]

This is exactly the case. Thanks for the good suggestions !