-
Notifications
You must be signed in to change notification settings - Fork 229
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
update meta map guidelines for reference file inputs #1987
base: main
Are you sure you want to change the base?
Conversation
❌ Deploy Preview for nf-core failed.
|
@ramprasadn there are some conflicts. |
|
||
3. All _non-mandatory_ command-line tool _non-file_ arguments MUST be provided as a string via the `$task.ext.args` variable. | ||
3. Non-file mandatory arguments or arguments needed to modify the command to make the module run with no error, SHOULD be provided as value channels (for example `lib_type` in [salmon/quant](https://github.com/nf-core/modules/blob/master/modules/nf-core/salmon/quant/main.nf)) - see 'Input/output options' below. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think rather than referring to 'non-file' in the current points 3. and 4. ... It would be better to separate that into its own bullet point. eg,
file
arguments, whether or not they are mandatory, should be provided as input channels (for example, thefai
argument in samtools faidx)
I'm torn as to whether that should come before or after the current point 3.
On the one hand, it seems like mandatory arguments are more important, and hence addressed first.
On the other, it is probably a more necessary reminder to include non-mandatory file arguments, which the author themselves may never use, as module input.
As discussed in the nf-core maintainers meeting, I have updated the guidelines for creating new modules to add a meta map to channel definitions that carry reference file inputs.