Code Linting Not Working Properly

[mynanshan]

Hello Positron community. I am very excited to try this VS-Code style editor integrated with excellent Rstudio features.

I found the code linting sometimes not working. See the following screenshot for an example:

In the function f = function(x) return(y), symbol y is not defined and should be reported in the diagnostics. In contrast, Rstudio marks this error correctly (this function can be enabled in Global Options):

The code linting may work partially and occasionally. Sometimes, the linter can detect part of the coding errors, but it does not find all errors, and the diagnostics may disappear after some time.

Has anyone experienced the same issue? Can/Will Positron support the Rstudio's code diagnostics? Or maybe an R-linter that resembles those for Python (e.g. Pylint, Pylance, Pyright)?

Version information:

Positron Version: 2025.02.0 build 171
Code - OSS Version: 1.96.0
Commit: 55f73310e900d46f5f472b4b7e2baa552aa2f157
Date: 2025-02-10T15:48:36.459Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Linux x64 6.11.0-17-generic

[juliasilge]

Can you say more about how you are generating those diagnostics in RStudio? I just tried this out and don't see diagnostics:

[mynanshan]

Hi. I think it is because I enabled the code diagnostics from Tools > Global Options > Code > Diagnostics in RStudio. After activating the "warn if no variable definition in scope", you should be able to get the warning.

[juliasilge]

I opened #6607 to track and prioritize this work. Take a look and see if you have anything additional to add!