Fix arrow function detection in JavaScript/TypeScript symbol extraction #169
+305
−39
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
The tree-sitter query files were missing patterns to match arrow functions. The key issue was that const/let use lexical_declaration (not variable_declaration). - Update JavaScript tags.scm to detect arrow functions, function expressions - Update TypeScript tags.scm to detect non-exported arrow functions - Add comprehensive test coverage for arrow function detection - Update golden test expectations Fixes #168
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
extract_symbolsMCP tool to detect JavaScript/TypeScript arrow functionslexical_declaration(used byconst/let)Changes
javascript/tags.scmto detect arrow functions, function expressions, exportstypescript/tags.scmto detect non-exported arrow functionsFixes #168