Not sure which account to tag, but <@U01NHAGGUBA> ...
# hackathon-oct-2025-versions-topics-adoption
p
Not sure which account to tag, but @Clint Valentine @Clint Valentine has written this plugin for collating topic versions: https://github.com/fulcrumgenomics/nf-versions Could be useful for the nf-core template perhaps?
n
I'm not entirely sure on this one TBH, it seems like an extra layer we would need to update for every new tool we add. I think the current topics approach handles this pretty well already. But still a nice project 👀
💯 4
👍🏻 1
m
we thought of something similar with @Edmund
👍🏻 1
but as @Nicolas Vannieuwkerke said, not happy with pushing an extra layers in modules
it's in #C08TKFDUNHG
so to be honest, if go down this road, I'd rather we use the nf-core-utils plugin
but I'd rather we find a smarter idea
s
Yeah, I do think that topics removes quite a bit of the need here
c
The plugin does take advantage of topics already. It just hardcodes the shell commands that are repeated everywhere in a single place that you can more easily import from. It also builds up the MultiQC YAML dynamically and doesn't do it through a bunch of
.yml
files everywhere. It be nice if there were native Nextflow features for introspecting environment metadata and passing that along, but that'd be a much bigger endeavour.
The plugin's just a 0.1.0 release so I'd caution folks from depending on it in projects as large as nf-core... it's pretty easy to copy-paste into nf-core utils if you like the abstraction.
I haven't been able to think of a more clever solution that uses pre-existing syntax. I don't really love all the copy-pasted version grepping code I have to put in all my Nextflow processes and stubs.