Fix strict syntax errors#491
Merged
JoseEspinosa merged 1 commit intodevfrom Mar 19, 2026
Merged
Conversation
|
Member
|
Thanks @bentsherman! Actually, we are working with @Kevin-Brockers in updating modules, so I think it would make sense to wait until #487 is merged to update this PR |
aa0125b to
0c65ff9
Compare
JoseEspinosa
approved these changes
Mar 19, 2026
Member
JoseEspinosa
left a comment
There was a problem hiding this comment.
LGTM! Thanks @bentsherman ❤️
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi, just testing the pipeline with strict syntax for Nextflow 26.04. Feel free to take these changes if they make sense
NOTE: nf-core modules and subworkflows can be fixed properly by just updating them from
nf-core/modules