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
The second method involves including an input of `type: File` in the script itself:
```cwl
class: CommandLineTool
inputs:
my_script:
type: File
inputBinding:
position: 0
# other inputs go here
baseCommand: sh
outputs: []
```
In the context of this entry, "the script" refers to the executable script the user wants to reference in the CWL file. I think the code describes how to make that script "an input of type:File", rather than how to put some CWL-specific data ("input of type:File") in that executable script.
The text was updated successfully, but these errors were encountered:
I think the code describes how to make that script "an input of type:File", rather than how to put some CWL-specific data ("input of type:File") in that executable script.
This is correct. Literally embedding a script is also possible, but only recommended for short scripts (maybe one screen of text).
Am I correct in understanding that the intention here was "including the script as an input of
type:File
in the CWL document itself"?user_guide/src/faq.md
Lines 115 to 132 in dd897f4
In the context of this entry, "the script" refers to the executable script the user wants to reference in the CWL file. I think the code describes how to make that script "an input of
type:File
", rather than how to put some CWL-specific data ("input oftype:File
") in that executable script.The text was updated successfully, but these errors were encountered: