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

Using *.code-workspace as the current project still makes it show up in the list #260

Closed
AndreasBackx opened this issue Mar 16, 2019 · 2 comments
Labels
depends on Depends on issues from VS Code duplicate enhancement

Comments

@AndreasBackx
Copy link

Perhaps related to #151, though I read on a few issues here that you could get multiroot projects to work by using the .code-workspace file as the rootPath, which indeed worked. However there seems to be a small bug. When one of these projects is activated, it still shows up in the list of projects when switching projects. Would this require #151 to be resolved first?

@alefragnani
Copy link
Owner

alefragnani commented Mar 19, 2019

Hi @AndreasBackx ,

Yes, this scenario is not yet supported (adding a .code-workspace in projects.json. So, you will have to wait for #151 to be officially released.

I'm thinking about to give up from microsoft/vscode#37421, because unfortunately, I don't see it being released soon 😞 .

Hope this helps

@alefragnani alefragnani added enhancement depends on Depends on issues from VS Code duplicate labels Mar 19, 2019
@alefragnani
Copy link
Owner

@AndreasBackx , that doesn't mean I would give up from supporting Workspaces. Just the way it should work 😁

Stay tuned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
depends on Depends on issues from VS Code duplicate enhancement
Projects
None yet
Development

No branches or pull requests

2 participants