aft_callgraph and aft_outline can't see interface methods or object-property functions (TypeScript) #329

Activity

1. aft-alfonso commented on Sep 22, 2026

   

   aft-alfonsoBot

   on Sep 22, 2026

   More actions

   Reproduced, and you have diagnosed it more precisely than most reports manage. Both blind spots are real and they are one cause.

   A nine-line fixture is enough:

   export interface Shape {
     area(): number;
     scale(f: number): Shape;
   }
   export const helper = {
     compute: function doCompute(x: number) { return x * 2; },
     arrow: (y: number) => y + 1,
   };
   export function plain(n: number) { return n; }

   aft_outline returns exactly three symbols:

   E interface Shape 1:4
   E const helper = 5:8
   E function plain(...) 9:9
   

   No area, no scale, no compute, no doCompute, no arrow. aft_zoom on area fails the same way your parse did.

   The cause is in symbol extraction rather than in the call graph, which is why you saw a healthy graph with a hole in it. Our TypeScript extraction never visits method_signature nodes inside an interface, and never treats a function expression or arrow assigned to an object property as a definition. The call graph is built from those symbols, so anything invisible to extraction is unreachable to callers, zoom and outline alike. Your observation that a plain export const parse resolves correctly while the interface method and the object property do not is exactly the shape that predicts.

   Your third point needs a different answer, and I would rather separate it than let it ride along. callers of ZodType reporting zero is not the same defect. The call graph records calls, and interface X extends ZodType or const s: ZodType is a type reference, not a call site — so zero callers is literally true and unhelpful. That is a missing capability rather than a broken one. Worth its own issue if you want type references traversable; say so and I will open it with your context rather than folding it in here silently.

   The part of your report I found most useful is the last paragraph. A model reaching for aft_callgraph first, getting symbol_not_found, and falling back to sixteen greps is the real cost — the tool that should have been the fast path is the one that failed, and it failed in a way that looks like absence rather than a gap. That is worse than being slow.

   Fix dispatched. I will comment here when it lands and again when a release carries it.
2. aft-alfonso commented on Sep 22, 2026

   

   aft-alfonsoBot

   on Sep 22, 2026

   More actions

   Fixed in v0.57.1.

   Your 9-line fixture reproduced it exactly. Two node kinds were never extracted:

   • method_signature — method declarations inside an interface
   • methods and arrow properties declared as object literal properties

   So those symbols were absent from aft_outline, from the symbol cache, and from anything downstream that resolves against extracted symbols.

   One detail worth flagging since it changes behaviour beyond the fix itself: because these symbols now exist, callgraph and search indexes re-extract on first run after upgrading. That is a one-time background pass, not a rebuild you need to trigger.

   Thanks for the minimal fixture — it made the missing node kinds obvious rather than something to guess at.
3. aft-alfonso

   closed this as completedon Sep 22, 2026