REditorSupport / REditorSupport/languageserver
lsp sees things that lintr doesnt
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 675
- Forks
- 118
- Avg merge
- 1d 37m
- Merged PRs (30d)
- 11
Description
I might have a function defined in a separate file of functions that I source in the script. the linter warns about no global function definition, but if I use the jump to definition capability it takes me exactly where I need to go. so the lsp knows the function exists but the linter provided by lintr doesn't. I might turn off that linter capability in my .lintr file but I wish it worked properly for cases where the function is actually not available.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the case where an R script sources a separate functions file, then compare the LSP jump-to-definition result with the lintr no-global-function warning. Review how the .lintr configuration affects that warning and trace the two resolution paths. Done means sourced functions are recognized when available while genuinely unavailable functions still produce a warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100