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] Improve the empty history message for guiding users to collections. #19242

Merged

Conversation

jmchilton
Copy link
Member

A driving motivator for the issue was initial impressions and histories without datasets and history-less landing pages. Just displaying a page about no datasets without regard to how to resolve that seems bad in all of those cases.

Maybe this was not intentional though because if you have some initial datasets - you get a second column with the ability to add more. Maybe just swapping to that column by default might be better instead of the message. If that is the case - feel free to treat this as a bug report and close this out.

How to test the changes?

(Select all options that apply)

  • Instructions for manual testing are as follows:
    1. Create a workflow with a list input, navigate to it with an empty history, and click the new orange button.

License

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

@ahmedhamidawan
Copy link
Member

Tried this locally with the openGlobalUploadModal method you've added here, and will say it does work out pretty nicely; no datasets, well, just upload some using the upload modal, then close that out to see the uploaded ones in the builder.

But since the CollectionCreatorModal already has the "Upload Files to Add to Collection" tab, maybe the better approach is to simply have that tab available still (like you mentioned)?

@jmchilton
Copy link
Member Author

@ahmedhamidawan - it is your component - if you'd like to put the extra work into getting that tab to appear and work then go for it. Conflicting upload modals if a mess to be sure. It sounds like that would be a better user experience - I just wanted to make sure we had something better than just that text before the 24.2 release.

@ahmedhamidawan
Copy link
Member

@jmchilton Here is an implementation:

no_items_collection_builder.mp4

If this looks good, should I just push this commit to ur branch?
we could

  • keep ur current commit
  • or I (or you) could rebase and remove it

This meant also adjusting the creator(s) content to prioritize the alert message with the link.
@ahmedhamidawan
Copy link
Member

I have pushed the commit
You could take a look and we could remove it/adjust for any changes etc.?

@ahmedhamidawan ahmedhamidawan added this to the 24.2 milestone Dec 3, 2024
@jmchilton
Copy link
Member Author

Absolutely lovely - way better than my hack!

@jmchilton jmchilton marked this pull request as ready for review December 4, 2024 14:52
@jmchilton
Copy link
Member Author

@ahmedhamidawan I opened the PR so I cannot merge this but you can! You've got a +1 from me on your changes.

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 for pointing this out John!

@ahmedhamidawan ahmedhamidawan merged commit f5cb35c into galaxyproject:release_24.2 Dec 4, 2024
27 of 28 checks passed

This comment was marked as resolved.

@nsoranzo nsoranzo deleted the improve_empty_message branch December 4, 2024 17:59
@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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/UI-UX kind/bug 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