fix: Go parser fails to extract a package-level variable usage #67
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Check the PR title.
(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 methodObjectType.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.