-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does WDL support optional outputs? #394
Comments
If I'm not mistaken cromwell does support optional outputs, just not on certain backends. In the development spec, the section on optional literals doesn't specifically mention inputs and there are examples of optionals being used outside of the input section (eg. in the conditionals section). There indeed don't appear to be any examples of optionals in the output sections. I'd agree that it might be good to add something there. |
true dat. but a different section says this: "A user does not need to specify a value for the parameter in order to satisfy all the inputs to the workflow." |
This is covered by the 1.1 spec. |
I see the section about optional inputs...with lots of nice examples and explanations....but I do not see a similar section about optional outputs
https://github.com/openwdl/wdl/blob/main/versions/1.0/SPEC.md#outputs-section
womtool (at least) thinks that outputs can be marked as optional, but Cromwell doesn't support that....the spec is inconclusive...
where the spec does talk about Optional types, it seems very biased about "inputs": https://github.com/openwdl/wdl/blob/main/versions/1.0/SPEC.md#optional-parameters--type-constraints
Even though optional types can be used throughout a wdl script and not only in the input section.
I think it would be good if the spec were more consistent about Optional types, and ideally, make sure to have examples and wording that supports a parameter having an optional type in all stages of the script (workflow input, task input, workflow variable, task output, workflow output).
The text was updated successfully, but these errors were encountered: