Fixing the bug: target_bed was missing in liftover - #320
Conversation
|
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 4.0.3. For more documentation on how to update your pipeline, please see the Synchronisation documentation. |
|
@nf-core-bot fix linting |
|
|
@nf-core-bot fix linting |
❌ nf-test failed with latest Nextflow versionNote Tests with Nextflow's latest version failed but it will not cause a CI workflow failure.
See the full run for details. |
|
@khersameesh24 can you. maybe review this? |
| // liftover high confidence bed file if given | ||
| // liftover bed files if given | ||
| ch_targets_bed.map{file -> tuple([id: "targets"], file)} | ||
| .mix(ch_bed.map{file -> tuple([id: "regions"], file)}) |
There was a problem hiding this comment.
Hi @kubranarci , this is a minor issue but I think file is a keyword in nextflow, maybe you can name the variable something else. This mostly works but might have unexpected behavior and would be hard to debug later. I think it also highlights the file variable in different color because it is a reserved keyword
There was a problem hiding this comment.
I see, thanks you! I will change it.
khersameesh24
left a comment
There was a problem hiding this comment.
@kubranarci, looks good, just a minor comment
|
@nf-core-bot fix linting |
PR checklist
nf-core pipelines lint).nextflow run . -profile test,docker --outdir <OUTDIR>).nextflow run . -profile debug,test,docker --outdir <OUTDIR>).docs/usage.mdis updated.docs/output.mdis updated.CHANGELOG.mdis updated.README.mdis updated (including new tool citations and authors/contributors).