Support virtual workspaces

[lszomoru]

👋 Hi there, Martin here, from the VS Code team.

Recently we've announced the Remote Repository feature 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 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.

Thanks for the support and the great work! ❤️

[dbreshears]

We should opt out for now and log a new issue for future to see which feature areas we can enable

[karolz-ms]

We have opted out for now. In future we might enable the extension in virtual workspace environments, but probably only for limited set of features such as editing Docker and Docker Compose files.

[bwateratmsft]

I think the only features we could support in a virtual workspace would be the language servers, which would probably also require some changes to eliminate any Node dependencies. I think the rest of the features actually require a Docker instance.