I’ve also implemented the use of the several new N...
# oncoanalyser
s
I’ve also implemented the use of the several new Nextflow features (strict syntax, channel topics, workflow outputs) on top of the 2.3.0 release as they will soon be required by nf-core (see this article); the changes to use these features will be included in one of the next oncoanalyser releases
🙌 3
p
Hi @Stephen Watts - this is great! But I'm a little confused, as #C04CQ1LK7U1 is currently ranking bottom in my health dashboard 🫠 😆 https://github.com/nf-core/strict-syntax-health#readme
😨 1
Are those fixes on the
dev
branch? That's where the above repo looks.
s
Oh no! The changes are in the
implement-new-nextflow-features
branch; I hadn’t at the time merged into
dev
as they were made targeting a Nextflow edge release and I’m yet to revisit since
The other self-imposed blocker is that I’m expecting the Hartwig folks to send across adjustments for the 3.0.0 release soon and I didn’t want them to have to deal with resolving conflicts etc
If the timeline sticks I’d hope to get the strict syntax and co changes merged in a couple of weeks
p
ahh ok good, that's fine then - I was worried that your changes were already in
dev
but that my script was still flagging errors for some reason
ok well hopefully they will suddenly drop to zero at some point in the future when you merge to dev! 🙂