galaxyproject / galaxyproject/foundry
Set legacy DSL1 support posture for Nextflow file and set pipelines
Open
priority/v2
roadmap/off
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 3
- Avg merge
- 1d 22m
- Merged PRs (30d)
- 63
Description
Source open question from `content/research/nextflow-workflow-io-semantics.md`:
> How much legacy DSL1 support should the cast skill keep for `file` / `set` pipelines versus flagging them as low-confidence?
Context:
- Fixture corpus includes ad-hoc pipelines using legacy `file` and `set` qualifiers.
- Newer guidance prefers `path` and `tuple`, but corpus-first extraction should decide whether to support older constructs or report lower confidence.
- The decision affects `summarize-nextflow` extraction, cast guidance, and downstream translation confidence.
Related: #168, #174.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.