Describe the bug
Creating a zip of the workspace root (either through right-clicking the area of the explorer view that does not contain any files, or through the command interface) causes the extension to attempt to save to a location that is outside the current workspace.
To Reproduce
Steps to reproduce the behavior:
Open a repo in vscode.dev.
Right click the explorer view within the area shown (see screenshot).
Select Zip Tools: Create a zip file from folder.
Extension status bars hangs at Saving... and loads indefinitely. Console shows error (below).
Expected behavior
The extension should not try to write outside of the workspace but should instead show an error. Perhaps it could also ask if the user would like to save it to the workspace root instead.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
What type of VS Code were you using when you encountered the problem?
vscode.dev
Additional context
Add any other context about the problem here.
[Extension Host] Error (FileSystemError): Unable to write file 'vscode-vfs://github/AdamRaichu/vscode-extensions.zip' (AdamRaichu/undefined: Request failed due to following response errors:
- Could not resolve to a Repository with the name 'AdamRaichu/undefined'.)
at Function.c (../../../vs/workbench/api/worker/extensionHostWorker.js:82:27160)
at Object.writeFile (../../../vs/workbench/api/worker/extensionHostWorker.js:82:25814)
Describe the bug Creating a zip of the workspace root (either through right-clicking the area of the explorer view that does not contain any files, or through the command interface) causes the extension to attempt to save to a location that is outside the current workspace.
To Reproduce Steps to reproduce the behavior:
Zip Tools: Create a zip file from folder
.Saving...
and loads indefinitely. Console shows error (below).Expected behavior The extension should not try to write outside of the workspace but should instead show an error. Perhaps it could also ask if the user would like to save it to the workspace root instead.
Screenshots If applicable, add screenshots to help explain your problem.
Environment What type of VS Code were you using when you encountered the problem?
vscode.dev
Additional context Add any other context about the problem here.