Closed denis-yuen closed 7 years ago
To add more information here:
The outputs should look more like
outputs:
outputParameterName:
type: File
outputBinding:
glob: "*$(input.output_file_name)"
The example that @SolomonShorser-OICR provided should result in a non-helpful error message currently. Create JUnit test that triggers the error message (you might be able to just use the above directly) and then fix the error by providing a better error message.
Looks better now on staging.dockstore.org Outputs
$ dockstore tool convert cwl2json --cwl Dockstore.cwl --json test.json
problems running command: cwltool --non-strict --validate Dockstore.cwl
stderr for command:
/usr/local/bin/cwltool 1.0.20170217172322
Resolved 'Dockstore.cwl' to 'file:///media/dyuen/Data/large_volume/testing/570/Dockstore.cwl'
Tool definition failed validation:
Dockstore.cwl:3:1: Object `Dockstore.cwl` is not valid because
tried `CommandLineTool` but
Dockstore.cwl:101:1: the `outputs` field is not valid because
Dockstore.cwl:103:7: item is invalid because
missing required field `id`
Thanks @k-cao FYI @SolomonShorser-OICR
:+1:
Feature Request
Desired behaviour
The following leads to an unhelpful NullPointerException
Exact filenames are not relevant Generate a more helpful message
See also @SolomonShorser-OICR
Environment (Browser or OS and Dockstore version)
Dockstore 1.1.1