mirror of
https://github.com/safishamsi/graphify.git
synced 2026-07-13 02:47:00 +00:00
Michal Harakal
71423a1efb
`extract_kotlin` previously emitted zero `calls` edges (and zero `raw_calls` entries) on the current PyPI grammar. The Kotlin branch of `walk_calls` only matched node type `simple_identifier`, but PyPI's `tree_sitter_kotlin` produces `identifier` for the equivalent plain-identifier node. The `simple_identifier` ↔ `identifier` rename is a generation gap between tree-sitter-kotlin grammar versions — older forks (and the JVM `io.github.bonede:tree-sitter-kotlin` binding) still use `simple_identifier`. Accept both names so the extractor works across grammar generations. Also widens `_KOTLIN_CONFIG.name_fallback_child_types` for the same reason (defensive — currently the `name` field path covers class/function name resolution, but if that field is dropped in a future grammar update the fallback would face the same rename). Tested against `tests/fixtures/sample.kt`: edges go from 6 (file-contains + class-method only) to 10 (adds 4 in-file `calls` edges resolved by the walker: - .get() → .buildRequest() @ L8 - .post() → .buildRequest() @ L12 - createClient() → Config @ L21 - createClient() → HttpClient @ L22). A new regression test `test_kotlin_emits_in_file_calls` asserts the four edges so this exact bug can't recur. Found via graphify-kmp (Kotlin Multiplatform port of graphify) — its `PythonParityTest` flagged 4 KMP-only edges that Python missed. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>