Open alexiswl opened 2 years ago
Hello @alexiswl
I agree that the class: File path: a/file/path
error should be fixed.
And I see how listing each possible type for a mixed type that is not an array of mixed types is messy. How do you think we should represent this situation?
My main problem was that cwltool --make-template 2>/dev/null | yq eval --tojson '.' -
crashed, but don't have a strong preference on how it should be rendered.
I would go with 2 where alternatives are commented out.
So:
lic_instance_id_location: # optional
- # type "File"
class: File path: a/file/path
- a_string # type "string"
Becomes something like
lic_instance_id_location: # optional File | string
- class: File
path: a/file/path
# - a_string
Expected Behavior
Tell us what should happen
cwltool --make-template
should create a valid yamlActual Behavior
Tell us what happens instead
An invalid yaml is created when input types are mixed.
Workflow Code
Workflow can be found here
Yields
Note the
lic_instance_id_location
: which can be of typestring
File
ornull
: see (https://github.com/umccr/cwl-ica/blob/main/workflows/dragen-germline-pipeline/3.7.5/dragen-germline-pipeline__3.7.5.cwl#L205-L214)Your Environment
cwltool --version