Skip to content

fix: Go parser fails to extract a package-level variable usage #67

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.

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
merged 1 commit into from
Aug 15, 2025

Conversation

angrychow
Copy link
Contributor

What type of PR is this?

Check the PR title.

  • This PR title match the format: <type>(optional scope): <description>
  • The description of this PR title is user-oriented and clear enough for others to understand.
  • Attach the PR updating the user documentation if the current PR requires user awareness at the usage level. User docs repo

(Optional) Translate the PR title into Chinese.

修复:Go parser 不能完整提取包级别的变量依赖关系

(Optional) More detailed description for this PR(en: English/zh: Chinese).

en: We discovered that for an expression like Object.Call(), the parser could only extract the dependency on the method ObjectType.Call() but failed to capture the dependency on the Object instance itself. This behavior is inconsistent with our LSP-based parsers for other languages, which correctly identify this dependency.

zh: 我们发现,对于 Object.Call() 这样的表达式,解析器只能提取出对 ObjectType.Call() 方法的依赖,却未能捕获到对 Object 实例本身的依赖。该行为与我们基于 LSP 的其他语言解析器不一致。

(Optional) Which issue(s) this PR fixes:

No correlated issue.

(optional) The PR that updates user documentation:

No correlated documentation.

@welkeyever welkeyever merged commit b106c84 into cloudwego:main Aug 15, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants