Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

The object_usage_linter won't acknowledge bindings from @import or @importFrom

Abierto
  • ¿Algo no está bien?
#1,595 0 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
r, typescript, vscode
Área
tooling

Línea de trabajo

Reproduce la advertencia con la configuración del paquete y el ejemplo R/test.R, y compara el panel Problems de VSCode con devtools::check() y lintr::lint("R/test.R"). Rastrea cómo la extensión vscode-R invoca el object_usage_linter empaquetado de lintr y cómo se gestionan @import y @importFrom. Se considera terminado cuando los bindings importados ya no producen advertencias falsas de .data en VSCode y las comprobaciones existentes de lintr siguen pasando.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug

Describe the bug
The object_usage_linter that comes installed with vscode-R's lintr won't recognize functions added to package scope via @import and @importFrom calls. The linter that runs via devtools::check() or calling lintr::lint() directly, however, will. As such, there seems to be a bug in the lintr that comes packaged with vscode-R but not in other instances of lintr.

To Reproduce
Steps to reproduce the behavior:

  1. Create an R package via the R console usethis::create_package("Test")
  2. Run usethis::use_mit_license()
  3. Open the package in VSCode where you have the R extension installed
  4. Import deplyr and ggplot2 in the DESCRIPTION file

Package: Test
Title: What the Package Does (One Line, Title Case)
Version: 0.0.0.9000
Authors@R:
person("First", "Last", , "[email protected]", role = c("aut", "cre"))
Description: What the package does (one paragraph).
License: MIT + file LICENSE
Imports:
dplyr,
ggplot2,
Encoding: UTF-8
Roxygen: list(markdown = TRUE)
RoxygenNote: 7.3.2

  1. Create an R file called test in the R directory R/test.R
  2. Paste these functions into test.R
#' Group rows by name
#'
#' This function groups the rows of a data frame by the column "name"
#' @param df A data frame.
#'
#' @import ggplot2
#' @return A grouped data frame.
#' @export
group_by_name <- function(df) {
  data_grouped <- df |>
    dplyr::group_by(.data$name)
  data_grouped
}

#' Group rows by size
#'
#' This function groups the rows of a data frame by the column "size"
#' @param df A data frame.
#'
#' @importFrom ggplot2 .data
#' @return A grouped data frame.
#' @export
group_by_size <- function(df) {
  data_grouped <- df |>
    dplyr::group_by(.data$size)
  data_grouped
}
  1. Run devtools::document() and devtools::load_all()
  2. Go to problems panel or hover over .data in each of the functions and note the no visible binding for global variable '.data' warnings.
Image
  1. Run devtools::check() and see that no errors, warnings, or notes arise
  2. Run lintr::lint("R/test.R") and see ℹ No lints found.

Can you fix this issue by yourself? (We appreciate the help)

No, attempting to reinstall the R, the vscode-R extension, and rlanguageserver have not helped. Here is my settings.json file:

{
    "git.autofetch": true,
    "git.confirmSync": false,
    "[r]": {
        "editor.defaultFormatter": "REditorSupport.r"
    },
    "r.rterm.mac": "/usr/local/bin/R",
}

Expected behavior
An @import or @importFrom call should update the global namespace such that the imported function is defined for the object_usage_linter in the lintr package included by the vscode-R extension.

Screenshots

Image

Environment (please complete the following information):

  • OS: macOS
  • VSCode Version: 1.99.0 (Universal)
  • R Version: R version 4.4.2 (2024-10-31)
  • vscode-R version: 2.8.4

Additional context
Folks have a lot of issues with the object_usage_linter in lintr but I didn't find any that pertain directly to this, and as mentioned above, this doesn't seem to be an issue when invoking lintr without the vscode-R extension.

Lenguaje dominante
TypeScript
Estrellas
1.2k
Forks
139
Merge medio
23 h 31 min
PR fusionados (30 d)
13

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de REditorSupport/vscode-R

Todos los issues de REditorSupport/vscode-R

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.