Skip to content

parameter normalization regression remains in params-file declarations #5987

Closed
@yttria-aniseia

Description

@yttria-aniseia

Bug report

#5661 doesn't fix kebab-case parameters specified in -params-file.

Expected behavior and actual behavior

regression described in #5655 applies to declarations in params-file, which, per documentation, should be equivalent to parameters passed in cli.

Parameters defined in the file are equivalent to specifying them directly on the command line

Steps to reproduce the problem

test.nf:

params.longParam = "unchanged"

workflow {
        log.info "${params}"
        log.info "${params.longParam}"
}

test.yaml:

long-param: kebab

test2.yaml:

longParam: camel

Program output

23.10.1

# nextflow run test.nf --long-param kebab
[long-param:kebab, longParam:kebab]
kebab
# nextflow run test.nf --longParam camel
[longParam:camel, long-param:camel]
camel
# nextflow run test.nf -params-file test.yaml
[long-param:kebab, longParam:kebab]
kebab
# nextflow run test.nf -params-file test2.yaml
[longParam:camel, long-param:camel]
camel

24.10.5

# nextflow run test.nf --long-param kebab
[longParam:kebab]
kebab
# nextflow run test.nf --longParam camel
[longParam:camel]
camel
# nextflow run test.nf -params-file test.yaml
[long-param:kebab, longParam:unchanged]
unchanged
# nextflow run test.nf -params-file test2.yaml
[longParam:camel]
camel

Environment

  • Nextflow version: 24.10.5

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions