Hi, I just saw this new way of setting the params for modules: In nextflow.config

params {
    module_args = ""
}
process {
    withName: "MYMODULE" {
        ext.args = params.module_args
    }
}

This way you can load the config for all the test in main.nf.test and only specify params.module_args only for the test where the value is different from “”. This has been done for 9 modules (gcta, ldak and regenie) and I’m currently reviewing a module using it. I quite like this solution and reduce a bit the main.nf.test file. What do you think ?

I think we’ve started doing that, but we never really formalized it

Should it be

ext.args = params.module_args

or

ext.args = { params.module_args ?: "" }

? I guess the first one should be sufficient ?

Not sure we should put much more time into this since we take the args as module inputs for statically typed modules. But looks good for now 😛

see https://github.com/nf-core/website/pull/4521

right

That will be quite the lot of changes 😅

just in time for DSL3

In gcta, ldak and regenie, you have in the nextflow.config

params {
    module_args = ""
}

process {
    withName: "REGENIE_STEP2" {
        ext.args = { params.module_args ?: "" }
    }
}

Isn’t it redundant ? you should simply need either to specify the default globally or use the closure ?

It’s been in the docs for a while now: nf-co.re/docs/…/testing#… ( it was me who proposed it )