Support virtual workspaces

👋 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! ❤️

[aeschli]

@nicooprat @oeg8168 Until Vetur has adopted this, you can set

        "extensions.supportVirtualWorkspaces": {
            "octref.vetur": true
        }     

For vetur to run, you also need to trust the workspace.

[aeschli]

Typescript provides limited support that is basically just looking at the current file and knows a set of bundled libraries.

For vue it would be great to at least get the grammars when in a virtual workspace. For that, the best solution would be to extract a simple language extension that contains the language definition and the grammars. That will be useful as well for untrusted workspaces as well as when running as a web extension.