Hi all, opinions wanted - I am writing a module th...
# modules
j
Hi all, opinions wanted - I am writing a module that takes the below inputs - the latter two val inputs are boolean flags that enable specific outputs via command-line flags. It was suggested to be in review that these could be dropped and left to the pipeline developer as flags in arguments, which I like the idea of - the only problem is that the flags take a file path rather than a prefix, so it's possible for the user to specify e.g.
--tblout prefix.tsv
or
--tblout prefix.tbl
or basically any other pattern (and this is a flat tabular table, so it's plausible a user might specify a bunch of things). Is there a good way to signal to the user that the module expects you to use a specific extension, so that it is captured by the outputs (is a pattern in the meta.yml file fine)?
Copy code
input:
    tuple val(meta), path(cmfile), path(seqdb)
    val(write_align)
    val(write_target)
m
If it could cause pipeline instability and requires a bit of knowledge on how to supply
ext.args
, I would actually recommend keeping these as
val
so the the interface to the user is simpler ( i.e. a true/false param, rather than asking the user to supply a custom config with a closure and make sure they use
$prefix
and the correct file ending )
this 2
👍 1