-
Notifications
You must be signed in to change notification settings - Fork 30
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
Disable adding pattern when search is empty #654
Labels
bug
Only issues that describe bugs.
pr-visualization
Issues that touch the visualization pr(oject) which means web and desktop features.
Comments
alschmut
added
bug
Only issues that describe bugs.
pr-visualization
Issues that touch the visualization pr(oject) which means web and desktop features.
labels
Jul 27, 2019
JaiJoPa
added a commit
that referenced
this issue
Sep 17, 2019
JaiJoPa
added a commit
that referenced
this issue
Sep 17, 2019
JaiJoPa
added a commit
that referenced
this issue
Sep 17, 2019
Yes, since you could have a rule that already excludes it, then you wouldn't be able to add another rule to exclude it and delete the old rule. |
JaiJoPa
added a commit
that referenced
this issue
Sep 20, 2019
11 tasks
alschmut
added a commit
that referenced
this issue
Sep 20, 2019
alschmut
added a commit
that referenced
this issue
Sep 20, 2019
alschmut
added a commit
that referenced
this issue
Sep 20, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Only issues that describe bugs.
pr-visualization
Issues that touch the visualization pr(oject) which means web and desktop features.
Bug
Expected Behavior
When the search pattern is empty
then the add-pattern-menu should disable the appropriate Hide/Exclude option
Actual Behavior
When the search pattern is empty
then all options (Hide/Exclude) are available to click inside the add-pattern-menu
When the search pattern is already inside the Hide/Exclude list
then the add-pattern-menu disables the appropriate Hide/Exclude option
Screenshots
Comments
The
searchBar.component.html
still contains some dead code, which was used before to disable the options depending on the amount of matching files/folders from the search.Question
Should we also disable the options, when no nodes match the pattern, like before or only when the pattern is empty?
Steps to Reproduce the Problem
Specifications
The text was updated successfully, but these errors were encountered: