nextflow-io / nextflow-io/nextflow
Allow feature flags only in pipeline code
@bentsherman is already working on this.
Since Jun 25, 2026.
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
Feature flags can be set in the main pipeline script or in the config, but it doesn't make sense for them to be in the config because they are inherent to the pipeline code.
For example, a pipeline is either using the output DSL or it isn't, there is no point in being able to set nextflow.preview.output in the config. Same applies to all other feature flags.
There is one exception, which is nextflow.enable.configProcessNamesValidation. This feature flag was added to suppress warnings that occur when setting module config for processes/workflows that are conditionally executed. Now that we have provided alternatives to setting ext and publishDir with process selectors, this feature flag can be deprecated.
Related: #5194
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.
Assessment
This issue has not been assessed yet.