Skip to content

feat: resolve local Go package calls safely #331

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Helweg merged 2 commits into from
Aug 29, 2026
Merged

feat: resolve local Go package calls safely #331

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
70dabcb
feat: resolve local Go package calls safely
Helweg Aug 29, 2026
567f406
fix: restore Go call resolution after rebase
Helweg Aug 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

- **Source-backed architecture context**: Added the portable `architecture_context` tool across OpenCode, MCP, and Pi. It produces deterministic, token-bounded repository maps with source-derived responsibility excerpts, cited community and boundary evidence, strict query and directory focus, graph-sparse source-directory fallback, uncertainty notes, precise follow-up tool calls, and optional Git-backed recent activity. Architecture planning evaluation now measures graded evidence relevance and actual response token cost.
- **Local JavaScript module graph resolution**: TypeScript and JavaScript call edges now resolve through local relative ES module imports, aliases, default and namespace imports, named re-exports, and `export *` chains. Resolution remains conservative for ambiguous or missing modules and exports, existing indexes migrate without re-embedding unchanged chunks, and graph coverage diagnostics report branch-aware resolved and unresolved totals by language.
- **Local Go package call resolution**: Direct, unshadowed Go function calls now resolve conservatively to a unique function declared by another eligible indexed file in the same directory and package. Selector calls, build-constrained files, incompatible test files, different packages or directories, and ambiguous targets remain unresolved, while package membership and source changes refresh affected callers without re-embedding unchanged chunks.
- **Workspace package call graph resolution**: TypeScript and JavaScript call edges now follow project-local package imports selected by root `package.json` workspace array or object patterns, including exclusions, ordered static ESM `node`, `import`, and `default` conditions, exact source-facing declarations, bounded safe single-wildcard entries, and safe package-relative subpaths. Discovery remains bounded to known project sources, exact and null or invalid declarations block broader fallbacks, wildcard precedence follows Node's deterministic package-export specificity, and malformed, encoded-traversal, `node_modules`, escaping, external, or duplicate mappings remain unresolved rather than being guessed. Root ownership, manifest changes, and the resolution-version migration refresh unchanged graph edges without re-embedding source chunks.

## [0.25.1] - 2026-08-23
Expand Down
Loading