-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add regex support to Search.dataSets #2432
Labels
enhancement
New feature or request
priority-medium
Not functioning - next quarter if capacity permits
Comments
Thank you for raising this enhancement request. |
JWaters02
added a commit
to JWaters02/zowe-cli
that referenced
this issue
Feb 18, 2025
JWaters02
added a commit
to JWaters02/zowe-cli
that referenced
this issue
Feb 18, 2025
JWaters02
added a commit
to JWaters02/zowe-cli
that referenced
this issue
Feb 22, 2025
4 tasks
JWaters02
added a commit
to JWaters02/zowe-cli
that referenced
this issue
Feb 22, 2025
Signed-off-by: JWaters02 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
priority-medium
Not functioning - next quarter if capacity permits
Is your feature or enhancement request related to a problem or limitation? Please describe
Searching is limited to only searching for a simple string.
Describe your enhancement idea
I would like to be able to use regex when searching datasets and members. The functionality exists in the z/OSMF API, however it is not implemented for datasets yet.
Describe alternatives you've considered
Provide any additional context
I have looked at the zowe-cli code and how I would implement this. There are two options:
searchJobs
has, which means to makesearchString
into an optional parameter, then add a new optional parameter alongside it calledsearchRegex
searchString
a required option, but add an optional boolean calledisRegex
or similar, which when true would call the API with theresearch
query instead of thesearch
one.I like option 1 more because it would be a standard implementation between jobs and datasets. However, unfortunately this would cause a breaking change (as
searchString
would have to be made optional), which I would prefer to avoid (to allow this feature to come sooner), so therefore option 2 would have to do. But please let me know what your thoughts on that are.This feature enhancement would also enable this enhancement on Zowe Explorer (which is ultimately what I want):
zowe/zowe-explorer-vscode#3234
The text was updated successfully, but these errors were encountered: