-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roadmap for Language Server #1
Comments
Good question. The fact is there were no plans. It lets me think of the following road map. Some of the items below may lead to developments of new packages. Short term and easy tasks
Medium term
Long term and/or difficult tasks
|
I think you really need to query the R session to do anything like detecting attached packages. R code can attach packages implicitly if they are in Probably you need something like nvimcom that provides bi-directional communication between the R process and the language server process, this will also let you do object completions easily. For completions it would also be nice if the package supported custom completions defined using R's |
They are different concepts. Language server would be useful in any R files to provide language support. For example, if you are developing an R package, I am quite sure that you don't run Hydrogen on top of the R files. Hydrogen is mainly useful if one is doing data analysis. |
I'll read more about the language server protocol, and might be interested in contributing in the future. |
@jimhester Discussing something like nvimcom is also too early for now. I also envision such implementation and have put into in the long term target. Didn't know that there is an option to specify custom completer. Thank for letting me know. |
As a Vim user who doesn't use Nvim-R (there are dozens of us!), I can't tell you how much I appreciate your work on this. Having the LSP is an order of magnitude improvement over life before. A long-term goal could also be supporting Rmarkdown documents. Even the smaller subset of features currently provided by the package would be really handy there too. Thanks! |
You must take care of supporting go to definition. |
We appreciate any contributions. If you want to contribute, I am happy to give some guidance. |
Do you know if there is any package for providing go to definition? Or you can do manually that by searching the workspace and choosing the one that matches the definition in the syntax. |
We will need to manually search for the definitions and apply the match. That's one of the reasons why I still haven't implemented it. |
Something else I want to ask you about. |
Which language server features are you planning on supporting?
linting / diagnostics are pretty easy, code prettying / formatting somewhat more difficult, although https://github.com/krlmlr/styler is a good step forward there. Robust refactoring and references doesn't really exist AFAIK, although https://github.com/r-lib/pkgapi is a start to mapping function references.
The text was updated successfully, but these errors were encountered: