-
Notifications
You must be signed in to change notification settings - Fork 348
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
VSCode Multiprojects workspace completion is not working #664
Comments
The Only way I get this one to work, is by swap the A <-> B project order in the workspace configuration. WARN code navigation does not work for the file '..../A/src/main/scala/....scala' because it doesn't belong to a build target. |
is there a way to index both Projects A and B and potentially many other projects in the same workspace. |
Thank you for reporting! Multi-root workspaces are currently not supported, this functionality is blocked by two feature requests which are reported in
A possible workaround is maybe to keep two separate VS Code windows for each project instead of registering a new workspace directory. Closing as a duplicate. |
I've hit this :( Virtually every project i work on is a multi-module project. |
maybe this is the right request to keep an eye on |
Describe the bug
Source code navigation not working when multiple projects workspace is used under VSCode
To Reproduce
Create a VSCode workspace with multiple Project A and B
Init a Scala Project in A with SBT
Init a Scala Project in B with SBT
Let A project be the first in the list
Let B project be the second in the list
Expected behavior
When navigating A project, source code navigation must be working
When navigating B project, source code navigation must also be working
Screenshots
.metals and .bloop is created under the project A only
Installation:
Additional context
Search terms
VScode multi projects workspace
The text was updated successfully, but these errors were encountered: