Skip to content

TypeScript: typed static getter chains lose CALLS edges while typed locals resolve #3009

Open

Description

@ChangeXJ

Version

codebase-memory-mcp 0.12.1

Platform

Windows (x64)

Install channel

GitHub release archive / install.sh / install.ps1

Binary variant

standard

What happened, and what did you expect?

A method call through an explicitly typed static getter is missing from the call graph, both in the same file and across a relative import. Reading the same getter into an explicitly typed local variable and then calling the method produces the expected edge. A same-file factory-method chain also works.

Expected: the two getter-chain callers in the reproduction produce CALLS edges to their respective target methods. Actual: all three control callers resolve, but both getter-chain callers are absent.

Tested executable SHA-256: 39f6a789cd858d7428561ac5afaefb9a47b018dcba0ad6fa41ae71a45e0ed656. This was reproduced on v0.12.1; current main was not built or tested. All code and results below come from newly written synthetic files, with no application code, private paths or business data.

Reproduction

Create an otherwise empty directory containing exactly these three files.

local.ts:

class LocalService {
    private static shared: LocalService = new LocalService();
    static get instance(): LocalService { return this.shared; }
    static create(): LocalService { return this.shared; }
    runLocal(): void {}
}

export function localViaGetter(): void {
    LocalService.instance.runLocal();
}

export function localViaFactory(): void {
    LocalService.create().runLocal();
}

export function localViaTypedVariable(): void {
    const service: LocalService = LocalService.instance;
    service.runLocal();
}

service.ts:

export class SharedService {
    private static shared: SharedService = new SharedService();
    static get instance(): SharedService { return this.shared; }
    runShared(): void {}
}

consumer.ts:

import { SharedService } from './service';

export function crossViaGetter(): void {
    SharedService.instance.runShared();
}

export function crossViaTypedVariable(): void {
    const service: SharedService = SharedService.instance;
    service.runShared();
}

Index in full mode with a fresh project name. Replace <ABSOLUTE_FIXTURE_DIR> with the directory containing those three files:

codebase-memory-mcp cli index_repository --repo-path "<ABSOLUTE_FIXTURE_DIR>" --name ts-getter-call-repro --mode full --persistence false
codebase-memory-mcp cli trace_path --project ts-getter-call-repro --function-name ts-getter-call-repro.local.LocalService.runLocal --direction inbound --depth 1 --include-evidence true
codebase-memory-mcp cli trace_path --project ts-getter-call-repro --function-name ts-getter-call-repro.service.SharedService.runShared --direction inbound --depth 1 --include-evidence true

To inspect the exact target edges through MCP, call query_graph with:

{
  "project": "ts-getter-call-repro",
  "query": "MATCH (a)-[r:CALLS]->(b) WHERE b.name = 'runLocal' OR b.name = 'runShared' RETURN a.name,b.qualified_name,r.strategy LIMIT 50",
  "format": "json",
  "max_rows": 50
}

Actual versus expected

Caller Target Expected edge Observed edge
localViaGetter LocalService.runLocal present missing
localViaFactory LocalService.runLocal present present
localViaTypedVariable LocalService.runLocal present present
crossViaGetter SharedService.runShared present missing
crossViaTypedVariable SharedService.runShared present present

The complete query result has exactly the three control rows shown in Logs (has_more: false, truncated: false). Inbound traces report 2 callers of runLocal instead of the expected 3, and 1 caller of runShared instead of 2. Both report callers_total_relation: eq on this tested release.

The fresh full index reports 20 nodes / 35 edges, with 0 skipped, 0 parse_partial, 0 parse_unusable, and 0 not-indexed files. check_index_coverage with diagnostics: full reports no_recorded_issue / metadata_match for all three fixture files, with coverage metadata version 9.

Scope and related issues

Possible investigation area

Source inspection of the v0.12.1 tag suggests checking how static getters are represented in the TS type registry and how member reads propagate their declared return type. lookup_member_type_inner() returns a method's function signature, while ast_sweep_shapes() handles class fields and constructor parameter properties without explicit getter-value handling. This is an investigation lead, not a tested patch.

A regression should assert the exact target edges for both getter callers while preserving the factory and typed-local controls. Cross-file and incremental-index paths should retain the accessor's value type, and ordinary method references should remain function values.

Logs

Complete target-edge query (3 rows, has_more=false, truncated=false):
crossViaTypedVariable -> ts-getter-call-repro.service.SharedService.runShared  lsp_ts_method
localViaFactory -> ts-getter-call-repro.local.LocalService.runLocal           lsp_ts_method
localViaTypedVariable -> ts-getter-call-repro.local.LocalService.runLocal     lsp_ts_method

Diagnostics trajectory (memory / performance / leak issues)


Project scale (if relevant)

Synthetic fixture only: 3 TypeScript files, 20 nodes / 35 edges

Confirmations

  • I searched existing issues and this is not a duplicate.
  • My reproduction uses shareable code (a dummy snippet or a public OSS repository), not proprietary code.

Activity

  1. added
    parsing/qualityGraph extraction bugs, false positives, missing edges
    ux/behaviorDisplay bugs, docs, adoption UX
    windowsWindows-specific issues
    on Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingparsing/qualityGraph extraction bugs, false positives, missing edgesux/behaviorDisplay bugs, docs, adoption UXwindowsWindows-specific issues

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions