Skip to content
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

Support multiple roots in a workspace #5188

Closed
amisevsk opened this issue Mar 9, 2020 · 1 comment · Fixed by #5033
Closed

Support multiple roots in a workspace #5188

amisevsk opened this issue Mar 9, 2020 · 1 comment · Fixed by #5033

Comments

@amisevsk
Copy link

amisevsk commented Mar 9, 2020

Is your feature request related to a problem? Please describe.
We would like to add Scala support to Eclipse Che. Che uses the Theia editor, which supports the language server protocol used in VS Code.

In Che, we start workspaces in a remote container and clone in a user-specified repo. This means that the "open folder" in the editor is /projects, with the Scala project imported into a subfolder (e.g. /projects/my-scala-sample). When this occurs, metals fails to initialize, as there is no build.sbt in the root folder (/projects).

Describe the solution you'd like
Support the "workspace folders request", as defined in the language server protocol as of 3.6.0.

Describe alternatives you've considered
The current workaround is that the user must open the subfolder into which their project has been cloned; this is a significant departure from how other language servers handle this (e.g. Go and Java both initialize without this issue).

Additional context

Search terms:
workspaceFolders, initializeParams, language server protocol

@tgodzik
Copy link
Contributor

tgodzik commented Mar 10, 2020

Thanks for reporting! This is something we plan to do, but will require a bit of refactor, so not sure when exactly we will be able to fix this.

It is something that I keep in my mind, as it would be useful in a number of scenarios.

This could also be a workaround for: #5907

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants