Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Extending stateful URLS with node filters and Expanding/collapsing modular pipelines flag #1799
Extending stateful URLS with node filters and Expanding/collapsing modular pipelines flag #1799
Changes from 46 commits
1bdd7ae
bfb8a66
ecbcdbb
8b49f52
11768e5
a2460b6
9c86282
25a7aff
8f5a152
17e100a
a726b70
ff643a5
ff55085
2106bf3
d763d11
fefbbdb
3d37c13
5c380f6
c69f4c2
7dfe800
db7b4dd
0c7b267
248ea6d
03c6b42
b80730b
fdc13cb
4397923
a300bed
719fb31
d176e7b
187b338
d90c158
5b65eb4
0a85e0e
5f41fea
885ac55
dc9317d
15c1113
2e74f1f
bfebde2
e93dbb5
9071420
4b016f9
47f5aa1
4919374
5c038b1
778ace5
ceacc74
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking maybe we can simplify this
setIsResetFilterActive(false) --> whenever the 'Reset' button is clicked
setIsResetFilterActive(true) --> whenever any tag, or filter is clicked.
So we avoid the complex logic below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think doing that will work if someone uses the UI to do filtering, but if someone directly changes the url, the reset button status should also watch out for the url.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
another suggestion is to follow the KISS principal and keep the
Reset
button always on but since this is also design suggestion looping @stephkaiserThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ravi-kumar-pilla @rashidakanchwala @stephkaiser I understand that the logic to set correct reset button status is complex, but are we keeping it simple like always ON or keeping what I did ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My suggestion is keeping it permanently enabled. Even when both the 'Reset' and reset filter are active, it doesn't alter the outcome. Many UI designs follow this convention, where the clear button remains visible even when the form is already empty. That's just my perspective, but would like to hear what others think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In case if we keep always ON,
If the user clicks the reset button while the filter is already in the default state, the state will still be set to the same values. In this scenario, if the user is zoomed in on the flowchart, it will also be reset.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi team, thanks for flagging to me. I think its confusing to users if the Reset button is always there even after they press it, theres no way for uses to tell they are on the default/reset view or the customised filtered view unless they look at the url. I think the convention is that when the reset/clear button is visible that implies that changes have been made and it can be reset to default (like when you've applied a filter on a website, a clear button will appear).
I wanted to ask what the default view is? because in my opinion it should be without any filters applied (nodes, datasets, parameters). Otherwise it's a bit confusing as it implies to users that a filtered view is the default, unless we want to make a filtered view the default then the Reset button will not be visible when those filters are applied.
What do you all think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The default view is set to 'Nodes', with 'Datasets' enabled and 'Parameters' disabled. Hence, we use 'Reset' instead of 'Clear' filters.
Since majority including design agree having 'Reset' enabled all the time might confuse users, I think maintaining the way as Jitendra had previously done seems ok. We can see how we can make it less complex.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sounds good. For me this is similar to a subscriber pattern. The Reset button status should subscribe to any changes in the query params. I am not sure of the technical feasibility in this ticket, but yes we can modify in future if need be.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another thought - we also shouldn't rely on a colour change in the Reset text to indicate that a change has been applied as this doesn't work with colourblind users.
Design fixes for the Reset button below: