Open bernt-matthias opened 2 years ago
Personal communication with @nsoranzo
We should use a different attribute than value
if we use regular expressions.
If we do this it should be something that we can evaluate on the client as well, otherwise we'll be dealing with loads of invalid workflow connections that we can't validate in the editor.
If we do this
You mean regular expressions? Maybe this can be a 2nd step...
Any new way to specify and evaluate conditionals, these are probably the biggest hurdle in creating workflows .
Few ideas to make conditionals more expressive:
allow for
when
tags match multiple options:<when value="option1,option2"/>
or<when value="option1|option2"/>
(with<when value="option*"/>
it might even be useful for dynamic options) which would solve https://github.com/galaxyproject/galaxy/issues/3428add something like an else branch for conditionals (e.g.
<else>
)allow when tags appear multiple times. which might allow for a more logical structuring of the tool form
allow
multiple="true"
for the select https://github.com/galaxyproject/galaxy/issues/7173allow
optional="true"
when
tagPotential problem: