Have you tried with Nextflow edge?

This is running with a fresh build of Nextflow, so it's even edgier than edge

😔

The error that I get for rnavar with

--help

is different to the one you posted about in the ambassadors channel: https://github.com/nf-core/strict-syntax-health/blob/main/lint_results/prints-help-results/rnavar_help.txt

Interesting

It's not just this pipeline, there are a bunch with the same error. So I suspect it's something that needs fixing in the template

Thanks, I'll have a look at putting this in TEMPLATE

Yeah I'm trying to transfer these subworkflows to plugins

I think what's happening here is that the implicit type casting of CLI params is disabled with strict syntax (see 25.10 deprecations) This is because the new

params

block will take care of this for you and we don't want the legacy type detection to interfere with that So my thinking was that existing pipelines should treat every param as a string, at least until migrating to the new

params

block In this case you should be able to fix it

<http://params.help|params.help> as Boolean

And it might be worth documenting this guidance somewhere

Ok so my fix works because it's checking that the string version of the param isn't

true

So what do I need to do if my help is not being printed? Change params.help to Boolean?

If you're using the centralised subworkflow, just wait for the above to be merged and then update.

You're right, looks like you have to just compare to "true" / "false" Here is the legacy type detection code for what it's worth: https://github.com/nextflow-io/nextflow/blob/295f17307c2d0effc3e7bd93923550a3cb47b[…]14c/modules/nextflow/src/main/groovy/nextflow/cli/CmdRun.groovy

ok cool, so then I think my PRs are the right way to do it / the right fix.. Right? 😅