Skip to content

Conversation

@maxulysse
Copy link
Member

PR checklist

  • This comment contains a description of changes (with reason).
  • If you've fixed a bug or added code that should be tested, add tests!
  • If you've added a new tool - have you followed the pipeline conventions in the contribution docs
  • If necessary, also make a PR on the nf-core/sarek branch on the nf-core/test-datasets repository.
  • Make sure your code lints (nf-core pipelines lint).
  • Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
  • Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
  • Usage Documentation in docs/usage.md is updated.
  • Output Documentation in docs/output.md is updated.
  • CHANGELOG.md is updated.
  • README.md is updated (including new tool citations and authors/contributors).

@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.0.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.

main.nf Outdated
versions = versions.mix(PREPARE_INTERVALS.out.versions)

vep_fasta = (params.vep_include_fasta) ? fasta.map{ fasta -> [ [ id:fasta.baseName ], fasta ] } : [[id: 'null'], []]
vep_fasta = (params.vep_include_fasta) ? fasta.map{ fasta_ -> [ [ id:fasta_.baseName ], fasta_ ] } : [[id: 'null'], []]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is the language server adding an underscore?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

because fasta is an already defined item, so we use _ after if the item is reused within the same scope or before is the item is dropped

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it hurts my eyes, but not going to argue with the language server

main.nf Outdated
versions = versions.mix(PREPARE_INTERVALS.out.versions)

vep_fasta = (params.vep_include_fasta) ? fasta.map{ fasta -> [ [ id:fasta.baseName ], fasta ] } : [[id: 'null'], []]
vep_fasta = (params.vep_include_fasta) ? fasta.map{ fasta_ -> [ [ id:fasta_.baseName ], fasta_ ] } : [[id: 'null'], []]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it hurts my eyes, but not going to argue with the language server

@bentsherman
Copy link

Can we get this merged? Or at least the syntax errors?

The next release of the VS Code extension comes with a custom Pipeline view, which uses the language server to display a tree view of workflows and processes. Due to these syntax errors, the language server isn't able to parse several files and as a result the Pipeline view is incomplete. Fixing these syntax errors should allow the language server to provide the entire call tree.

The variable name errors aren't essential for fixing the Pipeline view. But for what it's worth, you can rename those variables to whatever you want, it doesn't have to be _.

@FriederikeHanssen FriederikeHanssen added this to the 3.6 milestone May 12, 2025
@famosab
Copy link
Contributor

famosab commented Jul 14, 2025

Closed for #1912

@famosab famosab closed this Jul 14, 2025
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.

5 participants