-
Notifications
You must be signed in to change notification settings - Fork 3
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
Submit search on enter #805
Conversation
3d43087
to
9a7db86
Compare
b0f3b93
to
aa5dfa1
Compare
b655a04
to
49cdc95
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
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.
Just through usage on the website, I noticed a few inconsistencies. This is assuming we want the search field to still be populated with the search after hitting enter, and to have focus on the search bar. As well as after leaving the page, the filter would be removed
- Projects dashboard - Search field is emptied and not focused after search
- Groups dashboard - If I leave the groups dashboard page and come back, the search bar is still populated with the search but the groups are not filtered
- Data Exports - Search field is emptied and not focused after search
- Samples - Search and filter are still enabled after leaving and coming back to the page
- Project Files - Search field is emptied and not focused after search
I also think if the user clicks on the "X" at the end of the search bar, that should return an unfiltered request, thoughts?
Samples table search is expected to be different as we store that server side, but I agree with your remaining comments. |
…ted with sorted tables
This should be added back later
512a90b
to
5152882
Compare
This comment has been minimized.
This comment has been minimized.
@ChrisHuynh333 & @ericenns Those pages are updated along with tests |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
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.
Looks good to me!
Comments have been addressed, and I verified the changes
What does this PR do and why?
Describe in detail what your merge request does and why.
enter
key is pressed, not debouncedScreenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other pull requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Ensure that search still works across the project (tested through our integration tests as well)
PR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.