Files
codebase-memory-mcp/tests
Henry Hazan dc0f8ae642 fix(elixir): populate first_string_arg for Elixir calls
tree-sitter-elixir attaches no field name to a call's arguments node. Its whole
field set is key, left, operand, operator, quoted_start, quoted_end, right,
target and value, so ts_node_child_by_field_name(node, "arguments") is always
null for Elixir and call.first_string_arg was never populated for any Elixir
call.

Every downstream signal that keys off a call's string argument was therefore
dead for Elixir: Phoenix route paths, HTTP/async service URLs, and config keys.
Nothing reported an error — the field was simply always NULL.

The definition side already knows this: extract_defs.c carries
elixir_call_args() with a positional second-child fallback for exactly this
reason. This adds the same fallback on the call side, gated to `call` nodes,
since Elixir's other call kinds (`dot`, the `|>` binary_operator) carry no
arguments node in that position.

The new test pins the field directly rather than a downstream effect.

Signed-off-by: Henry Hazan <henry@teramine.io>
2026-08-19 01:35:17 +03:00
..
2026-06-28 13:05:05 +02:00