So regarding that: https://github.com/nf-core/seqinspector/pull/184 I used a hack since we don't have meta map in MultiQC. But to be honest, and I know @Jonathan Manning agrees with me, having the meta id encoded in such a way in the filename is less than optimal. How would people feel if I were to add a meta map for MultiQC? It could really be useful in case where you run multiple instance of MultiQC per run (ie per samples and so on).

For me, as soon as a module gets run more than once in an nf-core workflow it needs a meta map

and for me if you run a module more than once you need a tag

Fine by me, it doesn't hurt anyone

ok, I'll work on a PR then

I’d love a meta map in MQC, we use it too in our pipelines

This could definitely be usefull.

Made a little adjustment, let me know what you think https://github.com/nf-core/modules/pull/10277

Can you update multiqc_sav as well?

Done!

I'm still concerned about the linting

I’ll give it another go

oooh I see

nope it's a bug...parsing these things is a pain (until we have a tree-sitter 👀 ), but please make an issue so we can fix it

@Maxime Garcia, fixed the meta and linting

why changing the process name for MULTIQC_SAV?

module names can’t have underscores 😅

Oh I see

Kinda weird this wasn’t flagged when the module was originally merged, but it is what it is 🤷🏻

Maybe it's a recent check

@Delfina Terradas is working on getting it in #CL88J906S

Nice, I will have a look and put it in #C06PHJM0Y3D

🤔 isn’t #C06PHJM0Y3D more for fastq QC?

-> https://github.com/nf-core/seqinspector/blob/dev/modules/local/rundirparser/main.nf

aha 😄