-
Notifications
You must be signed in to change notification settings - Fork 648
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
camelCase params duplicated with hypens #2061
Comments
Yes, this was a choice made in the early days, I admin, not one of the best. |
What's more confusing is that the
params {
snake_case = 'foo'
camelCase = 'bar'
multiCamelCaseParam = 'baz'
}
println(params) $ nextflow config -flat .
params.snake_case = 'foo'
params.camelCase = 'bar'
params.multiCamelCaseParam = 'baz'
$ nextflow run .
N E X T F L O W ~ version 21.03.0-edge
Launching `./main.nf` [happy_brattain] - revision: ec72fcbcb3
[snake_case:foo, camelCase:bar, camel-case:bar, multiCamelCaseParam:baz, multi-camel-case-param:baz] This is actually a good thing in our case, as it means that we only need to add a workaround in the pipeline schema validation at run time, and don't need to patch any of the code in Phil |
I think it should be fixed with a big note in the cli docs |
Done ebfed09 |
Thank you! |
Bug report
Expected behavior and actual behavior
When using a
param
with camelCase, a duplicated copy is made with hyphens (camel-case
). I've never noticed this before, but the new @nf-core schema validation now warns about these params as they are unexpected.Expected behaviour would be to, well, not do this. 😀
Steps to reproduce the problem
Program output
More readable:
snake_case
:foo
camelCase
:bar
camel-case
:bar
multiCamelCaseParam
:baz
multi-camel-case-param
:baz
'cc @KevinMenden @Leon-Bichmann
The text was updated successfully, but these errors were encountered: