REditorSupport / REditorSupport/languageserver

specify what you mean by language server configuration

Open
#596 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
R
Stars
675
Forks
118
Avg merge
1d 37m
Merged PRs (30d)
11

Description

you say in the documentation:

Server capabilities are defined in capabilities.R. Users could override the capabilities by specifying the LSP configuration setting server_capabilities or options(languageserver.server_capabilities) in .Rprofile. For example, to turn off definitionProvider, one could either use LSP configuration

"r": {
    "lsp": {
        "server_capabilities": {
            "definitionProvider": false
        }
    }
}

or R options

options(
    languageserver.server_capabilities = list(
        definitionProvider = FALSE
    )

someone who knows R should be able to figure out that the R options can go into the .Rprofile but I am not sure what file this JSON example refers to, or where to put it; it would be nice if context was added for newcomers to LSP (like me);especially people coming from RStudio where we don't have to think about LSP. You could say 'LSP configuration via this file located at such and such location in linux/mac and such and such location in windows`. That would be helpful.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the documentation passage that references capabilities.R and the .Rprofile option. Identify and document where the JSON-based LSP configuration belongs on Linux, macOS, and Windows, adding enough context for users unfamiliar with LSP; the examples should make both configuration methods unambiguous.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.