Open t1m0thyj opened 7 months ago
Thank you for raising this enhancement request. The community has 90 days to vote on it. If the enhancement receives at least 10 upvotes, it is added to our development backlog. If it receives fewer votes, the issue is closed.
We may be able to test this extension and model after its behavior: https://marketplace.visualstudio.com/items?itemName=Kelvin.vscode-sshfs. Thanks to @VitGottwald for suggesting it 🙂
References that would need updated: https://github.com/zowe/zowe-explorer-vscode/blob/8103a68ec7195ce900e0751c06d604994ea2e33f/packages/zowe-explorer/src/configuration/Profiles.ts#L43 https://github.com/zowe/zowe-explorer-vscode/blob/8103a68ec7195ce900e0751c06d604994ea2e33f/packages/zowe-explorer-api/src/profiles/ProfilesCache.ts#L36
Is your feature request related to a problem? Please describe.
As a mainframe user who edits USS files with Zowe Explorer, I want to be able to add a USS directory to my VS Code workspace, So that I can easily develop a project hosted in USS on the mainframe
Describe the solution you'd like
Support adding USS directories as a folder in the active VS Code workspace (see screenshot below). Adding an action to the right-click menu on USS session nodes to "Add to Workspace" might also be nice. Consider supporting virtual workspaces for data sets too and loading project config files from the USS directory.
Describe alternatives you've considered
Currently I can enter a USS filter prompt in Zowe Explorer to open a USS directory, but there is no way to automatically re-open it when VS Code is reloaded and I can't view USS files alongside local files in the main Explorer panel.
Additional context
The FileSystemProvider implemented in #2777 lays the groundwork for virtual workspace support. I've created a PoC based on this in the test-fsp-virtual-workspace branch: