Closed bernt-matthias closed 10 months ago
The workaround is to use value=""
in the XML param
. It is true though that is a bit annoying and misleading that you cannot leave the attribute out.
Thanks for the hint. Sounds like this workaround could be implemented in the Galaxy code pretty easily (usually there are horrible side effects when I think like this). What do you think? Maybe a profile version?
I have a patch, working on tests now. No need to have profile changes.
Fixed in #16966 .
Describe the bug
Sometimes it's not possible to set a reasonable default for a tool parameter in the tool XML but users must set a value. This is currently not possible at least for numeric parameters and selects.
Numeric parameters produce an error like the following on tool loading.
Galaxy Version and/or server at which you observed the bug Galaxy Version: 23.1
Expected behavior
value
attribute can be omitted for tool definition user should not be able to submit the tool if no value is set.