nextflow-io / nextflow-io/nextflow
Legacy Groovy style typing is silently ignored
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
Legacy style Groovy typing does nothing and appears to be silently discarded with no lint or compile time indications:
workflow {
Fake v = 1
println v
}
This prints 1 and the completely made up type Fake, which doesn't exist anywhere seems to cause no issues at all.
I know that nextflow lint -format would convert this to def v: Fake = 1 which will then error as expected, but the current totally silent behaviour on plain lint and run seems wrong.
Environment
- Nextflow version: 26.04.6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the snippet with nextflow lint and run, then trace how legacy Groovy-style declarations are parsed and validated. Done means an undefined type such as Fake is no longer silently accepted, with coverage for the reported example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100