InitializeParams#rootPath is ignored
See original GitHub issueAccording to Language Server Protocol 3.0 InitializeParams contains both a rootPath
(though deprecated) and rootUri
(preferred). Both of these are supported in LSP4J.
In pre-0.1.0 versions of eclipse.jdt.ls, both getRootPath
and getRootUri
were checked (see this commit for when this changed).
This presents as an issue in Atom where ide-java, relying on atom-languageclient, is sending initialize calls with a rootPath
only. I’m opening a ticket with them to resolve this, but having eclipse.jdt.ls support both getRootPath
and getRootUri
would comply better with the spec.
See atom/ide-java#37 for resulting error.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Add context path to Spring Boot application - Stack Overflow
I am trying to set a Spring Boot applications context root programmatically. The reason for the context root is we want ...
Read more >Command: init | Terraform - HashiCorp Developer
The terraform init command initializes a working directory containing configuration files and installs plugins for required providers.
Read more >pyright/configuration.md at main - GitHub
ignore [array of paths, optional]: Paths of directories or files whose diagnostic output (errors and warnings) should be suppressed even if they are...
Read more >2.10.1 Initializing the Data Directory - MySQL :: Developer Zone
For some MySQL installation methods, data directory initialization is automatic, as described in Section 2.10, “Postinstallation Setup and Testing”.
Read more >Conventions - Remix
The path to the app directory, relative to remix.config.js. ... If a file matches, it will be ignored rather than treated like a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
If that’s the case language server authors need to do a better job at communicating what version they support and when they break compatibility.
My hope is that in the future there will not be any breakage since with 3.0 we introduced capabilities for the client which should now allow to make thing non breaking as long as servers and clients correctly check the capabilities.