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
Copy file name to clipboardExpand all lines: src/faq.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -246,7 +246,7 @@ inputs:
246
246
<a name="enuminputs"></a>
247
247
## Enum Inputs ⚜️
248
248
249
-
For command-line flags that require a specific input as the argument, an enum type can be declared in CWL. **Specifying null here is known as long form style. It does the same thing as the question mark on the other inputs.**
249
+
For commandline flags that require a specific input as the argument an enum type can be declared in CWL. **Specifying null here is known as long form style. It does the same thing as the question mark on the other inputs.**
250
250
251
251
```yaml
252
252
Format:
@@ -266,7 +266,7 @@ Format:
266
266
<a name="recordinputs"></a>
267
267
## Record Inputs 📀
268
268
269
-
For command-line flags that are either **mutually exclusive** or **dependent**, a special record type can be defined. You can also specify null here to create optional inputs.
269
+
For commandline flags that are either **mutually exclusive** or **dependent** a special record type can be defined. You can also specify null here to create optional inputs.
270
270
271
271
```yaml
272
272
#Using record inputs to create mutually exclusive inputs
0 commit comments