Skip to content

Fix graph resolution, coverage and query rendering - #47

Open
andrew wants to merge 12 commits into
mainfrom
fix/graph-correctness
Open

andrew wants to merge 12 commits into
mainfrom
fix/graph-correctness

Conversation

@andrew

@andrew andrew commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

Graph queries could include unrelated edges, and call resolution could select targets from shadowed imports, test-only declarations or unrelated receiver owners. This fixes those bindings and limits rendered queries to the selected edges, preserving distinct call sites.

Go method nodes retain receiver ownership, package and test scopes stay separate, and conflicting declarations remain unresolved. Python follows source submodules and static re-exports; Ruby follows literal require_relative loads to singleton and module_function bodies. Files with identical Ruby load closures share constant and method indexes. These joins use supplied source and leave ambiguous or unsupported calls external.

Recovered syntax errors now emit file warnings and set Complete=false. Graph fingerprints include Go module identity and ordered Python source roots. Regression coverage enters through Build and the CLI across Go, Python and Ruby.

Copilot AI balanced review requested due to automatic review settings October 5, 2026 19:31

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@andrew
andrew added this pull request to stack #49 October 5, 2026 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants