Files
codegraph/site/src/content/docs/core-concepts/resolution.md
T
4509b45dd5 Add landing page + Starlight docs site (#375)
* udpated matrix

* feat(site): add landing page + Starlight docs site

Astro + Starlight site in site/ — a flat/paper editorial landing page
plus 18 docs pages seeded from the README. Monochrome theme, hairline
rules, square corners, live GitHub star count, light default + dark
toggle. Deploys to GitHub Pages via .github/workflows/deploy-site.yml.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-24 13:21:25 -05:00

1.4 KiB

title, description
title description
Resolution & Frameworks How CodeGraph connects references and links routes to handlers.

Extraction produces nodes and raw edges; resolution turns names into real connections.

Reference resolution

After parsing, CodeGraph resolves:

  • Imports → the source files they point at (including tsconfig path aliases and cargo workspace members).
  • Calls → their definitions, by import resolution and name matching.
  • Inheritanceextends / implements between types.

Framework awareness

CodeGraph recognizes web-framework routing files and emits route nodes linked by references edges to their handler classes or functions — so querying the callers of a view or controller surfaces the URL pattern that binds it. See Framework Routes for the full list of recognized frameworks.

Dynamic-dispatch coverage

Static parsing misses computed and indirect calls, so flows can break at dynamic dispatch. CodeGraph bridges several of these boundaries with synthesizers so a flow connects end-to-end:

  • Callback / observer registration
  • EventEmitter channels
  • React re-render (setStaterender)
  • JSX child (render → child component)
  • Django ORM descriptors

Every synthesized edge is marked provenance: 'heuristic' with the site that wired it, and is shown inline wherever a path crosses it.