Typed workflows [wip]

Signed-off-by: Ben Sherman <bentshermann@gmail.com>

Author: bentsherman

adr/20260306-record-types.md

@@ -67,7 +67,7 @@ This function effectively creates an immutable map (`Map<String,?>`):
 
 - The keys are just field names
 - The values can have any type
-- The record can’t be modified -- use the `+` operator instead
+- The record can't be modified -- use the `+` operator instead
 
 Records can have arbitrary fields, unlike custom classes, which makes them easy to use with dataflow operators.
 

adr/20260310-typed-workflows.md

@@ -16,6 +16,6 @@ Some classes may be excluded from the above diagram for brevity.
 
 The `Nextflow` class implements several methods that are exposed to Nextflow scripts. See {ref}`stdlib-namespaces-global` for details.
 
-The `Channel` class implements the channel factory methods, and it is exposed directly to Nextflow scripts. See {ref}`dataflow-page` for details.
+The `Channel` class implements the channel factory methods, and it is exposed directly to Nextflow scripts. See {ref}`channel-factory` for details.
 
 The `Session` class is the top-level representation of a Nextflow run, or "session". See [nextflow.script](nextflow.script.md) for more details about how a `Session` is created.

docs/developer/nextflow.md

@@ -79,6 +79,7 @@ working-with-files
 process
 process-typed
 workflow
+workflow-typed
 module
 notifications
 secrets
@@ -133,6 +134,7 @@ reference/stdlib
 reference/process
 reference/channel
 reference/operator
+reference/operator-typed
 ```
 
 ```{toctree}
@@ -175,6 +177,8 @@ tutorials/rnaseq-nf
 tutorials/data-lineage
 tutorials/workflow-outputs
 tutorials/static-types
+tutorials/records
+tutorials/typed-operators
 tutorials/metrics
 tutorials/flux
 ```

docs/index.md

@@ -35,7 +35,7 @@ workflow {
 
 This syntax allows you to declare all parameters in one place with explicit type annotations, and it allows Nextflow to validate parameters at runtime.
 
-See {ref}`workflow-params-def` for details.
+See {ref}`workflow-typed-params` for details.
 
 (workflow-outputs-final)=
 
@@ -154,7 +154,7 @@ Type annotations can be appended with `?` to denote values can be `null`:
 def x_opt: String? = null
 ```
 
-In the type system, queue channels are represented as `Channel`, while value channels are represented as `Value`. To make the terminology clearer and more concise, queue channels are now called *dataflow channels* (or simply *channels*), and value channels are now called *dataflow values*. See {ref}`dataflow-page` for more information.
+In the type system, queue channels are represented as `Channel`, while value channels are represented as `Value`. To make the terminology clearer and more concise, queue channels are now called *dataflow channels* (or simply *channels*), and value channels are now called *dataflow values*. See {ref}`dataflow-legacy` for more information.
 
 Groovy-style type annotations (e.g., `String x`) are still supported for functions and local variables. However, the language server and `nextflow lint` will automatically convert them to Nextflow-style annotations during code formatting.
 

docs/migrations/25-10.md

@@ -63,7 +63,7 @@ The above example defines two processes. Their execution order is not determined
 
 When the workflow is executed, it creates two processes (`blast_search` and `extract_top_hits`) connected by the channel `query_ch`. Each process executes a task and emits a value for each input that it receives. Whenever `blast_search` emits a value, `extract_top_hits` receives it through the `query_ch` channel.
 
-See {ref}`process-page`, {ref}`dataflow-page`, and {ref}`workflow-page` to learn more about these features.
+See {ref}`process-page`, {ref}`dataflow-legacy`, and {ref}`workflow-page` to learn more about these features.
 
 ## Execution abstraction
 

docs/overview.md

@@ -1276,6 +1276,7 @@ The `run` command is used to execute a local pipeline script or remote pipeline
 
 `-dump-channels`
 : Dump channels for debugging purpose.
+: This option can specify one or more tags as a comma-separated list to only dump channels with a matching tag.
 
 `-dump-hashes`
 : Dump task hash keys for debugging purposes.