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] Fix inconsistent tab handling in invocation view #19298

Conversation

ahmedhamidawan
Copy link
Member

@ahmedhamidawan ahmedhamidawan commented Dec 10, 2024

Fixes #19286

consistent_tabs_invocation_view_2.mp4
Initial (outdated) change, with the added badge to the export tab
consistent_tabs_invocation_view.mp4

How to test the changes?

(Select all options that apply)

  • I've included appropriate automated tests.
  • This is a refactoring of components with existing test coverage.
  • Instructions for manual testing are as follows:
    1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

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

@ahmedhamidawan ahmedhamidawan marked this pull request as ready for review December 10, 2024 16:28
@github-actions github-actions bot added this to the 25.0 milestone Dec 10, 2024
Copy link
Member

@mvdbeek mvdbeek left a comment

Choose a reason for hiding this comment

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

nice!

@mvdbeek
Copy link
Member

mvdbeek commented Dec 10, 2024

looks like a round of prettier is needed

…onMetrics.vue

Co-authored-by: Marius van den Beek <m.vandenbeek@gmail.com>
@ahmedhamidawan ahmedhamidawan force-pushed the consistent_tabs_invocation_view branch from 74100e5 to 4532464 Compare December 10, 2024 16:46
Copy link
Contributor

@davelopez davelopez left a comment

Choose a reason for hiding this comment

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

Thanks for the unification!

I personally think that the exclamation badge and disabling the tab is a bit confusing.
For these reasons:

  • It draws a lot of attention "for a normal situation" and makes me think there is a problem in those tabs until I read the tooltip.
  • The visual state for a disabled tab is not very noticeable (besides for the extra exclamation badge) and requires extra code and style.

Those are not meant to be a -1, just my subjective opinion on UX 😅

Co-authored-by: David López <46503462+davelopez@users.noreply.github.com>
@ahmedhamidawan
Copy link
Member Author

ahmedhamidawan commented Dec 10, 2024

image

@davelopez @mvdbeek and folks in general, is this better?

There's even the primary variant:

image

@mvdbeek
Copy link
Member

mvdbeek commented Dec 10, 2024

Still looks good to me, I think the primary variant is more appopriate ?

@ahmedhamidawan
Copy link
Member Author

Moved the badge out to the tabs-end slot! ✅ @davelopez (updated screencast in description)
Hopefully this works better, I think it's an improvement!

@davelopez
Copy link
Contributor

davelopez commented Dec 10, 2024

Yes, this looks way better to me! Thank you!

The export invocation selenium test might need an update to wait for the correct event now that the tab is disabled 😅

@jmchilton
Copy link
Member

This is a very beautiful enhancement. So much polish!

Copy link
Contributor

@davelopez davelopez 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! 🙏

@davelopez davelopez merged commit 85d3631 into galaxyproject:release_24.2 Dec 11, 2024
30 of 33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Inconsistent Tab handling when running Workflow Invocations
4 participants