This repository was archived by the owner on Oct 31, 2026. It is now read-only.
Repository navigation
test: delete query tests - #82
Merged
Merged
Conversation
Delete the info-string query assertions, keeping the field assertion, since the fork maintains only full parsing. Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Why
The Maintenance Scope in
AGENTS.mdlimits this fork to full parsing and forbids testing queries, but query tests that still passed remained after the incremental-parsing tests were deleted.Requirements
queries/*.scm, and query-feature behavior), keeping full-parse assertions in mixed test files.queries/*.scmfiles,tree-sitter.json, and bindings published unchanged; only tests change.anglePrefixProofs.test.ts, because it only locatesemphasis,strikethrough,html_tag, and autolink nodes for tree-range assertions rather than testing query behavior.Customer Summary
No change to the published package; the test suite no longer checks query field matching.
Technical Summary
test/unit/fenceInfoString.test.tsloses its field and negated-field (!info_string) query assertions, which repeated itschildForFieldName('info_string')assertion; that assertion and thehasErrorcheck stay, under a title that no longer mentions queries.Testing
bun run verify,bun run build/ci, andbun wb test test/unit/fenceInfoString.test.tspass. The remaining suite runs in CI.