Open traeok opened 5 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.
I'm still new to virtual workspaces (through the GitHub Repositories VSCE), however, modifying the .code-workspace
manually doesn't sound very fun. 😅
I think people might prefer opening folders and saving the workspace via VSCode itself 😋
Need to investigate if REST APIs can handle wildcards and if this can be done without breaking changes. Could potentially be implemented as a new search API since URIs may not be well-suited to handle wildcards.
Is your feature request related to a problem? Please describe.
Currently, resource URIs are considered static paths to resources added to the provider. A suggestion was made to enhance our handling of these URIs to support wildcard/globs, mainly so that virtual workspaces can define patterns without having to define a URI for each entry they want in their workspace.
Describe the solution you'd like
Support wildcard patterns in resource URIs (data sets, USS, maybe jobs)
Describe alternatives you've considered
You can add an entry in your
.code-workspace
file for each entry you want, but this can be tedious especially if you want several entries from a matching pattern.