Deferred from PR #1101 review.
Original reviewer comment: #1101 (comment)
Context:
The tree-sitter-groovy grammar produces juxt_function_call nodes for Groovy command-style calls like foo bar(x). Neither the JS source-of-truth extractor (src/extractors/groovy.ts) nor the new Rust port (crates/codegraph-core/src/extractors/groovy.rs) dispatches this node kind, so these calls are silently dropped from the call graph.
This is a parity-equal bug in both engines, not a regression introduced by #1101. Fix should:
- Add
juxt_function_call" arm to extractGroovySymbolsinsrc/extractors/groovy.ts` so the JS extractor handles command-style calls.
- Add
juxt_function_call" arm to match_groovy_nodeincrates/codegraph-core/src/extractors/groovy.rs` to mirror.
- Add a fixture test exercising command-style calls (e.g.
task someTask { ... } Gradle DSL pattern).
Deferred from PR #1101 review.
Original reviewer comment: #1101 (comment)
Context:
The tree-sitter-groovy grammar produces
juxt_function_callnodes for Groovy command-style calls likefoo bar(x). Neither the JS source-of-truth extractor (src/extractors/groovy.ts) nor the new Rust port (crates/codegraph-core/src/extractors/groovy.rs) dispatches this node kind, so these calls are silently dropped from the call graph.This is a parity-equal bug in both engines, not a regression introduced by #1101. Fix should:
juxt_function_call" arm toextractGroovySymbolsinsrc/extractors/groovy.ts` so the JS extractor handles command-style calls.juxt_function_call" arm tomatch_groovy_nodeincrates/codegraph-core/src/extractors/groovy.rs` to mirror.task someTask { ... }Gradle DSL pattern).