You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
array: If itemSeparator is specified, add prefix and the join the array into a single string with itemSeparator separating the items. Otherwise first add prefix, then recursively process individual elements.
However, it does not mention how to behave in the case of the combination of itemSeparator and prefix in the different levels.
Note: I guess few users write such CWL document but platform developers have to care such cases. I hope we can define this corner case not to make difficult to implement platforms.
The text was updated successfully, but these errors were encountered:
By processing inputBinding in the leaf level in the above example, we obtain [["-pre", "elem1", "elem2", "elem3"], ["-pre", "elem"]].
Possible behavior
itemSeparator is applied for all the elements. that is: "-pre,elem1,elem2,elem3,-pre,elem"
itemSeparator is applied for the first element? "-pre elem1 elem2 elem3,-pre elem"?
It causes another problem: how to interpret string[] as string?
Reject when inputBinding has itemSeparator and any leaves (including their sub-leaves) specify the case of:
separate: true if prefix is specified, and
itemSeparator is not specified for arrays
I prefer the last choice for both cases, that is, rejecting such corner cases.
It makes easier to implement platforms and also enables to delay the decision until we know the real use cases for them.
Related: common-workflow-language/common-workflow-language#783
The spec of
CommandLineBinding
says:However, it does not mention how to behave in the case of the combination of
itemSeparator
andprefix
in the different levels.Current behavior:
tests/nested-array-inputBinding.cwl
tests/nested-array-inputBinding-job.yml
Result
Note: I guess few users write such CWL document but platform developers have to care such cases. I hope we can define this corner case not to make difficult to implement platforms.
The text was updated successfully, but these errors were encountered: