Re: [galaxy-dev] optional="false" not working?
On Fri, Aug 17, 2012 at 12:39 AM, Peter Cock wrote: > On Fri, Aug 17, 2012 at 12:18 AM, Dan Tenenbaum wrote: >> Hello, I have the following wrapper: >> >> >> foo >> >> tool.py $outputFileName >> >> >> > optional="false"/> >> >> >> >> >> >> >> I expect that when I click "Execute" I will be told that "tp" must >> have a value. However, that doesn't happen, it just goes ahead and >> executes the script. >> How do I get Galaxy to require that a text param have a value? >> Thanks, >> Dan > > Probably is has the value of an empty string? That seems > logical but unhelpful - and explains the behaviour ;) OK. I'll buy that. But perhaps when type="text", optional="false" should treat the empty string as though there is no value. > > You can probably use a validator in the XML for this (e.g. insist > on at least one character). This worked for me: Thanks very much! Dan > > Peter ___ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
Re: [galaxy-dev] optional="false" not working?
On Fri, Aug 17, 2012 at 12:18 AM, Dan Tenenbaum wrote: > Hello, I have the following wrapper: > > > foo > > tool.py $outputFileName > > >optional="false"/> > > > > > > > I expect that when I click "Execute" I will be told that "tp" must > have a value. However, that doesn't happen, it just goes ahead and > executes the script. > How do I get Galaxy to require that a text param have a value? > Thanks, > Dan Probably is has the value of an empty string? That seems logical but unhelpful - and explains the behaviour ;) You can probably use a validator in the XML for this (e.g. insist on at least one character). Peter ___ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
[galaxy-dev] optional="false" not working?
Hello, I have the following wrapper: foo tool.py $outputFileName I expect that when I click "Execute" I will be told that "tp" must have a value. However, that doesn't happen, it just goes ahead and executes the script. How do I get Galaxy to require that a text param have a value? Thanks, Dan ___ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
