NEXTFLOW IMPORTS BEING RELATIVE TO THE SCRIPT NOT ...
# rants
i
NEXTFLOW IMPORTS BEING RELATIVE TO THE SCRIPT NOT PROJECT ROOT shakefistshakefistshakefist
p
Not with modules from the Nextflow Registry 🙂
i
Context: moving a subworkflow from
<http://subworkflow.nf|subworkflow.nf>
to
subworkflow/main.nf
breaks all imports
i
Nice
p
can you use
$projectDir
or something? 🤔
i
Is migrating to registry modules on the nf-core roadmap? I don't recall seeing it mentioned anywhere
p
We have sort of loosely talked about it (mostly that we could potentially retire a fair bit of nf-core machinery) but not in any concrete manner yet. It'd be a good topic for the #C069B2Z5P1R channel!
n
Does using the nextflow module registry come with some kind of module versioning?
p
Yup
nf-core ones are a bit weird because they come from git, so they get
0.0.0-[commit hash]
, eg https://registry.nextflow.io/modules/nf-core/abra2@0.0.0-6c4ed3a
n
I see, thats pretty cool