Created
May 7, 2021 09:44
-
-
Save aeschli/f5af2d9b3b136122219745777eb9fdf0 to your computer and use it in GitHub Desktop.
virtual workspaces issue
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
👋 Hi there, Martin here, from the VS Code team. | |
Recently we've announced the [Remote Repository feature](https://code.visualstudio.com/updates/v1_56#_remote-repositories-remotehub) that lets you browse and edit files and folders directly on GitHub. | |
`Open Remote Repository...` opens VSCode on a folder or workspace located on a virtual file system. We call this a __virtual workspace__. We observed that not all extension support this well, either because they can not, or they haven't thought about it. | |
It would be fantastic if you could test whether your extension can handle virtual workspaces: | |
Check out the [Virtual Workspaces Extension Author Guide](https://github.com/microsoft/vscode/wiki/Virtual-Workspaces) on how to do that. | |
When done, set the new `virtualWorkspaces` capability in your 'package.json'. | |
``` | |
{ | |
"capabilities": { | |
"virtualWorkspaces": true | false | |
} | |
} | |
``` | |
- Use `"virtualWorkspaces": true` if your extension is prepared for virtual workspaces | |
- Use `"virtualWorkspaces": false` if your extension should be disabled when a virtual workspace is opened | |
For questions and comments please use the [Virtual Workspaces Tracking Issue](https://github.com/microsoft/vscode/issues/123115). | |
Thanks for the support and the great work! ❤️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment