Skip to content

Go: query-surface parity with Python (locate, overviews, call-graph verbs, imports, modules, dependencies) #447

Open

Description

@rahlk

Is your feature request related to a problem? Please describe.
PR #444 (de642a3) gives Go the full L3/L4 dataflow surface. But the GoAnalysis facade does not have the query surface below, which Python (and Java) already expose. So caller code that ports between languages fails on Go for these accessors.

Python name Go status at de642a3
callers_of / callees_of Missing. Go has get_callers / get_callees (cldk/analysis/go/go_analysis.py). These are direct-edge lookups by callable id, not the Python closure verbs.
get_modules Missing. get_symbol_table() returns Dict[str, GoModule], so the data is present without the accessor.
get_imports Missing. The data is present on GoModule.imports: List[GoImport] (cldk/models/go/models.py).
get_dependencies Not on the facade. Both backends implement it only to raise ARTIFACT_LAYER_UNAVAILABLE (codeanalyzer/codeanalyzer.py, neo4j/neo4j_backend.py), because the AnalysisBackend ABC requires it.
locate, locate_many Missing.
get_callables_overview, get_method_bodies Missing. Go has no projections.py (out of SDK3 scope until now).
call_paths_between, has_resolution_edges Missing.

Describe the solution you'd like

  • Add each accessor in the table to GoAnalysis, with the signature of its PythonAnalysis counterpart.
  • Make both backends (GoCodeanalyzer, GoNeo4jBackend) answer identically, including the miss paths.
  • Keep get_dependencies raising with a clear message until cango emits the artifact layer.
  • Add tests for each accessor on both backends.
  • Update CLAUDE.md (supported-languages table) and docs/agent-api-reference.md (Go section) in the same change.

Describe alternatives you've considered
Callers can read get_symbol_table() and GoModule.imports directly for modules and imports. This works, but it is not portable across languages.

Additional context
Refs #422, #426, #436.

Activity

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

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions