New process syntax Adoption
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 322
- Forks
- 255
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
Optional from Spring 2026
Template: November 2026
Required: Spring 2027
Ask @bentsherman if parameters will still be accessible in closures used in the configuration e.g.:
ext.args = { (meta.single_end && params.fragment_size > 0) ? "-fs ${params.fragment_size}" : '' }
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
Start by asking @bentsherman whether parameters remain accessible in configuration closures, using the shown ext.args example as the test case. The issue names no files, tests, or entry points, and does not define the implementation scope or completion criteria for adopting the new process syntax.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100