mirror of
https://github.com/colbymchenry/codegraph.git
synced 2026-11-04 08:45:36 +08:00
Colby McHenryandClaude Opus 4.8
44fb978597
Ruby's primary composition mechanism is the mixin (`include`/`extend`/`prepend` a module), but these parse as a bare `call` to a method named `include` with the module as a constant argument, so they created no edge — a concern module mixed into a class recorded no dependent unless its methods happened to be called in-repo. On a concern-heavy codebase (Rails) that was a large share of modules, and ActiveRecord is built almost entirely on `include`d concerns. Detect `include`/`extend`/`prepend` (bare, no receiver) in the Ruby extractor's visitNode hook and emit an `implements` edge from the enclosing class/module to each module argument (`constant` or `scope_resolution`), so editing a concern surfaces every class that mixes it in. Skips `extend self` / dynamic args, and `arr.include?(x)` (has a receiver) is unaffected. Measured (fair cross-file dependent coverage, symbol-bearing source files): rails/activerecord 84.8% → 93.0%, sidekiq 71.0% → 76.8%. Node count stable (edges only). Residual is genuine frontiers: classes instantiated by class-string `constantize` (associations, Arel nodes), generators, version files, and config/`require`-loaded components. Full suite green; Ruby-only change. (Follow-up: resolve `require`/`require_relative` to files — helps explicit-require gems like sidekiq; Rails autoloads so it benefits less.) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>