-
Notifications
You must be signed in to change notification settings - Fork 192
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
Remove hyphens from pipeline names in Nextflow workflows #3365
Comments
We could also reduce the number of workflows so this only affects one workflow in total, but this is a bigger issue. I.e. the hierarchy would be from:
To:
Cut out the middle man workflow. |
I just ran into this when using (I'm not sure if this is the best place to open User story: I'll make a new pipeline and I'll call it Then, the first time I run it: ERROR ~ Script compilation error
- file : github/colinbrislawn/ex-ample/main.nf
- cause: Not a valid include module name @ line 16, column 1.
include { EX-AMPLE } from './workflows/ex-ample'
^
Script compilation error
- file : github/colinbrislawn/ex-ample/main.nf
- cause: Workflow definition syntax error -- A string identifier must be provided after the `workflow` keyword @ line 28, column 9.
workflow COLINBRISLAWN_EX-AMPLE { |
@colinbrislawn the easy workaround is to replace all Do it as a separate commit and Git will sort out template merging in future. This shouldn't be too hard a problem to solve but someone needs to find time to do it. |
Understand! I left a comment because If there is a better place to put this story please let me know! |
Description of feature
There's a common convention outside of nf-core to call your pipeline
nf-${thing}
, but in doing this we add a hyphen which is an invalid Nextflow workflow name.It's an easy fix shortly after creation to remove the hyphen, but we can replace all hyphens with strings while creating the subworkflow names.
The text was updated successfully, but these errors were encountered: