-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/nextflow upgrade 23 10 0 #77
Conversation
Release/v0.7.1
Release/v0.7.2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, amazing effort to add the val()
qualifier everywhere, I approve these changes.
Some changed I would like to see:
- Long input or output tuples/lines (aka >127 characters)
- Inconsistency in whitespaces
I do see some inconsistencies in use of whitespaces. Sometimes a whitespace is added:
tuple (.....)
vs tuple(...)
And there are some whitespaces before the closing brackets:
tuple(emit: fake)
vs tuple ( emit: fake )
and whitespaces after a comma:
val(a),val(b), val(c)
vs val(a), val(b), val(c)
vs val(a),val(b),val(c)
Could you fix these inconsistencies as well to tuple(val(a), val(b), emit: fake)
?
Did you check whether deprecated functions/operators are used anywhere?
https://www.nextflow.io/docs/latest/dsl1.html#channels
https://www.nextflow.io/docs/latest/dsl1.html#operators
This reverts commit 1d4f005.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok!
Refactor of the in- and output variables so that the workflows can be run with Nextflow 23.10.0