nextflow-io / nextflow-io/tree-sitter-nextflow
Parse failure: stdout output with emit: and no comma
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Summary
A stdout output with a named emit: and no comma fails to parse.
Repro
Observed in one corpus file. Reduced example:
output:
stdout emit: log
Why it's hard
emit_declaration expects a comma before named options (path "x", emit: y). The stdout qualifier takes no value, so there is no comma before emit:. Making the comma optional makes emit_declaration conflict with input_declaration. Needs a stdout-specific output form that allows emit:/topic: directly.
Scope note
Single file. Low priority.
Measured against grammar dc5bda3; 1 of 8 remaining failures.
Contributor guide
No contributing guide indexed for this repository
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 with the grammar rules named in the issue, especially emit_declaration, input_declaration, and the stdout output form, then reproduce the reduced example output: stdout emit: log. Done means this input parses successfully without introducing conflicts with input declarations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100