Skip to content

parameter normalization regression remains in params-file declarations #5987

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
yttria-aniseia opened this issue Apr 19, 2025 · 0 comments · Fixed by #5989
Closed

parameter normalization regression remains in params-file declarations #5987

yttria-aniseia opened this issue Apr 19, 2025 · 0 comments · Fixed by #5989
Labels

Comments

@yttria-aniseia
Copy link

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants