Go: external receiver calls resolve to unrelated local interface methods

[ignazio-ingenito]

CodeGraph 1.4.1 on linux-x64 attributes calls on a concrete external receiver (database/sql.DB) to same-named methods declared by an unrelated local interface.

Minimal fixture:

type InternalStore interface {
    Exec(string, ...any) (sql.Result, error)
    QueryRow(string, ...any) *sql.Row
}

type Target struct { conn *sql.DB }

func (target *Target) Write() error {
    _, err := target.conn.Exec("insert")
    return err
}

func (target *Target) Read() *sql.Row {
    return target.conn.QueryRow("select")
}

After codegraph init, codegraph callees Write --json reports Exec at the InternalStore declaration, and codegraph callees Read --json reports QueryRow at the InternalStore declaration. Target neither imports an internal implementation nor declares that it implements InternalStore.

Expected: calls resolve to database/sql.DB when supported, or remain external/unlinked. They should not create an internal dependency on InternalStore.

Actual JSON excerpts:

{"name":"Exec","kind":"method","filePath":"flow/flow.go","startLine":7}
{"name":"QueryRow","kind":"method","filePath":"flow/flow.go","startLine":8}

The positive fixture chain StartImport -> loadManifest -> PersistLineage is resolved correctly, so the failure is specific to generic receiver-method precision.

[colbymchenry]

Fixed in #1316 (merged to main, ships in the next release), following exactly the policy you proposed: external receivers stay unlinked rather than creating internal dependencies.

Root cause: for a chained receiver (target.conn.Exec), extraction dropped the chain and emitted a bare Exec, which exact-name matching bound to the only Exec in the project — your unrelated InternalStore. Chained Go field calls now resolve through two validated inference hops (receiver's type from the method signature, field's declared type from the struct definition) and only that way:

• conn *sql.DB → external → no edge. Your fixture is a pinned regression test asserting Write/Read never appear as callers of the interface's declarations.
• In-project field types — including unexported ones — now gain correct edges that never existed before: on go-chi/chi this newly resolves mx.tree.FindRoute / InsertRoute / routes through the unexported tree *node field, all validated against the target type.
• Package-qualified types are followed only when the package is in-module, so handler http.Handler can't bind a same-named local type either.

Your positive-control chain (StartImport → loadManifest → PersistLineage) is unaffected — plain function calls don't touch this path. codegraph index -f after upgrading rebuilds the edges.