microsoft / microsoft/vscode-mono-debug
Support virtual workspaces
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 180
- Forks
- 182
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 1
Description
👋 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": trueif your extension is prepared for virtual workspaces - Use
"virtualWorkspaces": falseif 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! ❤️
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the extension's package.json and read the linked Virtual Workspaces Extension Author Guide. Test whether the extension works with a virtual workspace, then set the capabilities.virtualWorkspaces value to true or false as appropriate. Use the linked Virtual Workspaces Tracking Issue for questions or comments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100