Skip to content

Conversation

@fasterius
Copy link
Contributor

@fasterius fasterius commented Jan 20, 2026

This PR contains (non-exhaustive) changes related to both the new Nextflow strict syntax, as well as some harmonisation and increased readability across the pipeline code.

PR checklist

  • This comment contains a description of changes (with reason).
  • Make sure your code lints (nf-core pipelines lint).
  • Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).

Separate long lines containing e.g. extensive maps and process calls
with many inputs to increase code readability. Additionally, some minor
formatting and harmonisation throughout.
@nf-core-bot
Copy link
Member

Warning

Newer version of the nf-core template is available.

Your pipeline is using an old version of the nf-core template: 3.3.2.
Please update your pipeline to the latest version.

For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation.

@fasterius fasterius requested a review from nictru January 20, 2026 09:45
@nictru
Copy link
Collaborator

nictru commented Jan 20, 2026

Amazing thanks! I have been thinking about doing something like this! Will look at it soon

@fasterius
Copy link
Contributor Author

No worries! I asked for a review a little prematurely, gotta fix some issues first, so no rush.

@fasterius
Copy link
Contributor Author

I think I'm going to need some help with these conflicts, @nictru. You've removed some tests and there's the new condition_col meta variable, and I'm not entirely sure how it fits into my refactoring for the strict mode. If you like we can have a Zoom and do it together.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants