Description
Describe the bug
Sorry for the title, not sure how to put it in a few words.
When I enter a non-existant path into the USS filter, as expected the error appears to say path name not found.
However, when clicking the filter button again to enter a new path, the error appears twice more, because it is still trying to filter on the non-existant path.
Also, I don't know if this is a seperate bug or intentional, but when I enter to filter on dataset or jobs profile, it also refreshes the USS filter, so the error still comes up.
To Reproduce
Steps to reproduce the behavior:
- On USS profile, enter invalid path into filter and submit it
- See error that path name not found
- Click filter on USS profile again
- See same error that path name not found, x2
Expected behavior
I expect that when I get a path name not found error, the filter that I entered is "removed" (not from history, but from what it is trying to currently filter on).
Screenshots
Desktop (please complete the following information):
- OS: Windows 10
- Zowe Explorer Version: 3.1.0
- (Optional) Zowe CLI Version:
- (Optional) Are you using Secure Credential Store?
Additional context
Metadata
Assignees
Labels
Type
Projects
Status
Medium Priority
Activity