Skip to content

Commit 613bd90

Browse files
committed
AbstractWorkflowStep needs to be marked as 'abstract: true'
1 parent c575cad commit 613bd90

File tree

1 file changed

+10
-9
lines changed

1 file changed

+10
-9
lines changed

Workflow.yml

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -480,7 +480,7 @@ $graph:
480480
The value of `inputs` in the parameter reference or expression must be
481481
the input object to the previous iteration of the workflow step (or the initial
482482
inputs for the first iteration).
483-
483+
484484
485485
- name: ScatterMethod
486486
type: enum
@@ -504,6 +504,7 @@ $graph:
504504
- name: AbstractWorkflowStep
505505
type: record
506506
extends: [Identified, Labeled, sld:Documented]
507+
abstract: true
507508
docParent: "#Workflow"
508509
doc: |
509510
A workflow step is an executable element of a workflow. It specifies the
@@ -655,9 +656,9 @@ $graph:
655656
producing a job for every combination of the scattered inputs. The
656657
output arrays must be flattened to a single level, but otherwise listed in the
657658
order that the input arrays are listed in the `scatter` field.
658-
659+
659660
# Conditional execution (Optional)
660-
661+
661662
The condition is evaluated after `scatter`, using the input object
662663
of each individual scatter job. This means over a set of scatter
663664
jobs, some may be executed and some may be skipped. When the
@@ -689,30 +690,30 @@ $graph:
689690
docParent: "#Workflow"
690691
doc: |
691692
# Iterative execution (Optional)
692-
693+
693694
The `loop` field controls iterative execution. It defines the input
694695
parameters of the loop iterations after the first one (inputs of the
695696
first iteration are the step input parameters, as usual). If no
696697
`loop` rule is specified for a given step `in` field, the initial
697698
value is kept constant among all iterations.
698-
699+
699700
When a `loop` field is present, the `when` field is mandatory. It is
700701
evaluated before each loop iteration and acts as a termination condition:
701702
as soon as the `when` expression evaluates to `false`, the loop terminates
702703
and the step outputs are propagated to the subsequent workflow steps.
703-
704+
704705
The `outputMethod` field describes how to deal with loop outputs after
705706
termination:
706707
707708
* **last** specifies that only the last computed element for each output
708-
parameter should be propagated to the subsequent steps. This is the
709+
parameter should be propagated to the subsequent steps. This is the
709710
default value.
710-
711+
711712
* **all** specifies that an array with all output values computed at the
712713
end of each loop iteration should be propagated to the subsequent steps.
713714
Elements in the array must be ordered according to the loop iterations
714715
that produced them.
715-
716+
716717
Iterative execution in CWL is an optional feature and is not required
717718
to be implemented by all consumers of CWL documents. An implementation that
718719
does not support iterative executions must return a fatal error when

0 commit comments

Comments
 (0)