Skip to content
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

[24.2] Various list of pairs builder usability fixes. #19248

Merged

Conversation

jmchilton
Copy link
Member

  • Disable buttons when they don't make sense.
  • Don't auto-pair on empty filters.
  • Don't auto-pair at the start if nothing matches - the user did nothing wrong and we're scaring them with red buttons and all the data disappearing - if we cannot auto-pair the datasets we should just give them manual control and let them do it - the component is much simpler to understand with this new behavior in the no-matches case.
  • Update an old Galaxy green to the newer style.

The cognitive load of not needing to understand the filters if they don't work out is so much lower. Jumping into the component with wrong filters pre-configured and hiding your data is confusing, scary, and generally unpleasant I think.

How to test the changes?

(Select all options that apply)

  • This is a refactoring of components with existing test coverage.

License

  • I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

@jmchilton jmchilton force-pushed the list_pairs_usability branch from 8f985a3 to 072b209 Compare December 5, 2024 14:42
@jmchilton jmchilton added the release-testing-24.2 Issues stemming from 24.2 release testing process and PRs to address them label Dec 5, 2024
@jmchilton jmchilton force-pushed the list_pairs_usability branch from 072b209 to 6d0305c Compare December 5, 2024 20:44
Disable the button and make it clear in the message it has to do with empty filters.
How is a shade of green so evocative of a time.
It results in hiding all the data and a scary red messages when the user did literally nothing wrong. I think this is single biggest issue - it makes it seem like you cannot just manually pair these quickly.
@jmchilton jmchilton force-pushed the list_pairs_usability branch from 6d0305c to 0cc2bab Compare December 5, 2024 22:25
@jmchilton
Copy link
Member Author

A lot of failing stuff but it looks all unrelated to me.

@jmchilton jmchilton marked this pull request as ready for review December 6, 2024 14:13
@github-actions github-actions bot added this to the 25.0 milestone Dec 6, 2024
Copy link
Member

@ahmedhamidawan ahmedhamidawan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @jmchilton for these improvements!!!

Co-authored-by: Ahmed Hamid Awan <qe66653@umbc.edu>
@jmchilton jmchilton merged commit 0a11a41 into galaxyproject:release_24.2 Dec 9, 2024
46 of 54 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dataset-collections area/UI-UX kind/bug kind/enhancement release-testing-24.2 Issues stemming from 24.2 release testing process and PRs to address them
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants