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

[21.09] Show error message when history id is invalid #12985

Merged
merged 5 commits into from Dec 7, 2021

Conversation

OlegZharkov
Copy link
Contributor

@OlegZharkov OlegZharkov commented Nov 25, 2021

An error discovered by @wm75 and @bgruening
This PR shows an error on fetching history with an invalid id. As a nice bonus, I removed jquery from this component (not sure what was the purpose of putting it there)

How it's now:
https://usegalaxy.eu/histories/view?id=randomid

After this fix:

image

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

@github-actions github-actions bot added this to the 22.01 milestone Nov 25, 2021
@OlegZharkov OlegZharkov changed the base branch from dev to release_21.09 November 26, 2021 12:32
@OlegZharkov OlegZharkov changed the title fix showing history error [21.09] fix showing history error Nov 26, 2021
@dannon dannon merged commit 7ef39f6 into galaxyproject:release_21.09 Dec 7, 2021
@github-actions
Copy link

github-actions bot commented Dec 7, 2021

This PR was merged without a "kind/" label, please correct.

@OlegZharkov
Copy link
Contributor Author

Thanks @dannon @mvdbeek !

@mvdbeek mvdbeek changed the title [21.09] fix showing history error [21.09] Show error message when history id is invalid Feb 15, 2022
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.

None yet

5 participants