Fix Bash heredoc attachment after opening statements - #178
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #164.
Moves heredoc payload parsing to the statement terminator, so the complete opening redirect, list, or pipeline is parsed before the body becomes valid. The external scanner now queues multiple pending delimiters and serializes that state for incremental parsing.
Regression coverage includes trailing redirects, pipelines, semicolon-separated commands, empty bodies, indented heredocs, and multiple queued heredocs.
Validated with the pinned Tree-sitter 0.26.12 corpus tests, Bash negative/roles/lint gates, sweep smoke, workspace tests, Bash WASM check, and 15 incremental edits with zero fresh/incremental divergences.