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
Rename module info subcommand to module view (#7052) [ci fast]
* Rename `module info` subcommand to `module inspect`
Keep `info` as a backward-compatible alias. Adds a generic
`getAliases()` hook on `CmdBase` so subcommands can declare extra
names, and wires it through `CmdModule` so both the JCommander parser
and the usage/help lookup recognize aliases.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com>
* Rename subcommand to `module view` and update docs
Switch the new name from `inspect` to `view`. The `info` alias is
still kept for backward compatibility. Update the CLI reference,
module guide and 26.04 migration notes to reflect the new name.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com>
* update docs
Signed-off-by: Ben Sherman <bentshermann@gmail.com>
* update class names
Signed-off-by: Ben Sherman <bentshermann@gmail.com>
---------
Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com>
Signed-off-by: Ben Sherman <bentshermann@gmail.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-authored-by: Ben Sherman <bentshermann@gmail.com>
Copy file name to clipboardExpand all lines: docs/cli.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -323,19 +323,19 @@ See {ref}`cli-module-list` for more information.
323
323
324
324
### Viewing module information
325
325
326
-
The `module info` command displays detailed metadata and usage information for a specific module from the registry.
326
+
The `module view` command displays detailed metadata and usage information for a specific module from the registry.
327
327
328
328
Use this to understand module requirements, view input/output specifications, see available tools, or generate usage templates before installing or running a module.
329
329
330
330
```console
331
-
$ nextflow module info nf-core/fastqc
332
-
$ nextflow module info nf-core/fastqc -version 1.0.0
333
-
$ nextflow module info nf-core/fastqc -output json
The output includes the module's version, description, authors, keywords, tools, input/output channels, and a generated usage template showing how to run the module. Use `-json` for machine-readable output suitable for programmatic access.
337
337
338
-
See {ref}`cli-module-info` for more information.
338
+
See {ref}`cli-module-view` for more information.
339
339
340
340
### Running modules directly
341
341
@@ -358,7 +358,7 @@ $ nextflow module run nf-core/salmon \
358
358
-resume
359
359
```
360
360
361
-
Process inputs can be specified like params on the command line. For example, `--reads reads.fq` corresponds to the `reads` input in the `nf-core/salmon` module. Run `nextflow module info nf-core/salmon` to see the available params for the module.
361
+
Process inputs can be specified like params on the command line. For example, `--reads reads.fq` corresponds to the `reads` input in the `nf-core/salmon` module. Run `nextflow module view nf-core/salmon` to see the available params for the module.
The output includes the module description, authors, keywords, tools, inputs, outputs, and a ready-to-use command-line template. Use `-o json` to get machine-readable output.
0 commit comments