Skip to content

[19.01] Backport #7466: Don't display outputs that aren't going to be produced in workflow editor#7576

Merged
dannon merged 3 commits intogalaxyproject:release_19.01from
mvdbeek:backport_no_output
Mar 22, 2019
Merged

[19.01] Backport #7466: Don't display outputs that aren't going to be produced in workflow editor#7576
dannon merged 3 commits intogalaxyproject:release_19.01from
mvdbeek:backport_no_output

Conversation

@mvdbeek
Copy link
Member

@mvdbeek mvdbeek commented Mar 21, 2019

@innovate-invent ran into this recently and I think in general people have trouble identifying the outputs that a tool actually generates. If you connect a non-existing output or make it a workflow output that workflow will stop scheduling at that step, so this makes it much harder to generate invalid or partially running workflows.

mvdbeek added 3 commits March 21, 2019 20:25
This obviously doesn't work (yet) with filters that work
on the input dataset, but this already removes a lot of
outputs that arent' going to be produced based on static
options. Since exceptions default to priduing the dataset
this isn't much harm.
@dannon dannon merged commit 22f9e33 into galaxyproject:release_19.01 Mar 22, 2019
@martenson martenson added this to the 19.05 milestone Mar 22, 2019
@martenson martenson deleted the backport_no_output branch March 22, 2019 13:41
@galaxyproject galaxyproject deleted a comment from galaxybot Mar 22, 2019
@martenson martenson modified the milestones: 19.05, 19.01 Mar 22, 2019
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.

5 participants