-
Notifications
You must be signed in to change notification settings - Fork 6
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
Handle 'default' values and "minOccurs=0" in CWL from WPS-1 #17
Closed
10 tasks done
Tracked by
#141
Labels
ci/tests
Tests of the package and features
feature/CWL
Issue related to CWL support
process/wps1
Issue related to WPS 1.x processes support
triage/feature
New requested feature.
Comments
fmigneault
added a commit
that referenced
this issue
Jun 21, 2019
fmigneault
added a commit
that referenced
this issue
Jul 4, 2019
3 tasks
fmigneault
added a commit
that referenced
this issue
Jul 5, 2019
fmigneault
added a commit
that referenced
this issue
Aug 22, 2019
… formatting invalid schema json response
This was referenced Apr 6, 2020
This was referenced May 5, 2020
fmigneault
added a commit
that referenced
this issue
Feb 25, 2021
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
ci/tests
Tests of the package and features
feature/CWL
Issue related to CWL support
process/wps1
Issue related to WPS 1.x processes support
triage/feature
New requested feature.
ref #12, #11
CWL: how to set default values
(1) https://www.biostars.org/p/221531/
Common Workflow Language User Guide - Essential Input Parameters
(2) https://www.commonwl.org/user_guide/03-input/
More details here:
(3) https://www.biostars.org/p/286135/
"default"
generates"type": ["null", <other-real-type>]
and"<type>?"
is a shorthand for this sametype
definitiontodo
"default"
is present for aLiteralData
value"default"
is present for a"File"
reference"minOccurs"=0
is present for aLiteralData
value ("default"
as"null"
)"minOccurs"=0
is present for a"File"
reference ("default"
as"null"
)"maxOccurs">1
is present for aLiteralData
value (coverted to"type": "array"
)"maxOccurs">1
is present for a"File"
reference (coverted to"type": "array"
)"<type>?"
by itself, and with every combination of above cases, as well as with multiple cases combined (validate all situations are handled correctly)"minOccurs">1
, type should be converted toarray
automatically,maxOccurs
should be updated accordingly toarray
methods as above.extra
"allowedValues"
is present with a list of allowed values, which should resolve asenum
type (relates to AllowedValues missing from process descriptions #41)"allowedValues"
+ ("default"
and/or"minOccurs"=0
and/or"maxOccurs">1
) are present, to validate that everything still resolves properly [see ref (3) for more details about potential failure for"enum?"
]edit
Could introduce new CWL methods to define int/float Range or string AllowedAalues (similar to enum) following outcome of common-workflow-language/common-workflow-language#764
For Workflows, see developments related to following spec:
The text was updated successfully, but these errors were encountered: