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

[23.1] Fix workflow invocation detail reactivity #16369

Merged

Conversation

mvdbeek
Copy link
Member

@mvdbeek mvdbeek commented Jul 4, 2023

If you run a workflow from the submission screen without first populating the store by loading workflow instances through the invocation menu you would notice that the "steps" tabs panel is missing (to reproduce click "Run" from the workflow editor). I think the computed ensures a that the store return value is tracked as a reactive dependency (as opposed to using the ref alone), but would appreciate confirmation that that is indeed what fixes the bug.

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.

This fixes reactivity of the composable when the workflow isn't already
in the store, e.g. when looking at the details component loaded after
submitting a workflow.
@mvdbeek mvdbeek force-pushed the workflow_invocation_detail_fix branch from a61f8c5 to 50d5ea5 Compare July 4, 2023 14:15
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.

Looks good!

@mvdbeek mvdbeek merged commit 51e3b55 into galaxyproject:release_23.1 Jul 4, 2023
12 of 14 checks passed
@dannon dannon modified the milestones: 23.2, 23.1 Sep 22, 2023
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

3 participants