make argument attribute optional (true by default) in <param> from <inputs> during export

[khillion]

Hi,

I realized that if we do not precise that positional = True, the argument attribute is automatically added to any <param>.

What do you think if we remove this behaviour and just let the author decide the presence of this attribute like any other optional one?

Thanks.

[hexylena]

My thoughts:

• Argument was added to map the CLI flag to Galaxy in a better way than specifying it at the end of the help="". This way:
  • The galaxy user of a tool could get an idea of which flags correspond to the command line flags, and maybe run from command line with the same flags
  • A colleague was using the reverse mapping and providing CLI wrappers for galaxy tools. His users could invoke the CLI tool and the parameters would go to the correct places in Galaxy.
• Adding the flag was part of IUC best practices, but those docs have not been updated to reflect the new argument option.

Let me phrase it this way, if you wish to add an option to gxt.Tool or tool.export() that enables / disables the argument, I think that would be fine, but I would prefer to use the IUC best practices as a default state.

[khillion]

Thanks, I get it now! I think using the IUC best practices is the way to go so let's add an option to either gxt.Tool or tool.export().