Repository navigation
Add experimental syntax_range tool - #157
Merged
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
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.
Summary
Add an experimental offline
syntax_rangetool for structural range selection before anchored edits.This change introduces a Go parser-backed
syntax_rangecapability behind the newsyntax_rangesexperimental flag. It returns smallest-to-largest enclosing ranges plusread_file(anchors=true)hints, so the agent can safely flow from local structural targeting intoedit_anchoredwithout requiring an LSP server.It also wires the feature through TUI, oneshot, and dispatch child registries, adds parser/tool/TUI tests, and documents how
syntax_rangerelates tolsp_selection_ranges.Related issue
None.
How was this tested?
go test ./internal/lsp ./internal/agent ./internal/tuigo test ./...go vet ./...Observed:
go vet ./...was cleanChecklist
go test ./...passesgo vet ./...is cleandocs/guide)