fix(go): fill File-level metadata for pre-parsed packages#198
Merged
Conversation
b633713 to
6dbb3c2
Compare
When a package was pre-parsed via cross-module referCodes, only Functions were populated but File.Package/Imports were left empty. This broke downstream reachability analysis based on the package import graph. Now we still fill File-level metadata for such packages while skipping duplicate function-body parsing. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
6dbb3c2 to
d24c104
Compare
Duslia
approved these changes
Jun 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
fix
Check the PR title.
(Optional) Translate the PR title into Chinese.
(Optional) More detailed description for this PR(en: English/zh: Chinese).
en:
When a package was pre-parsed via cross-module referCodes, only Functions were populated but File.Package/Imports were left empty. This broke downstream reachability analysis based on the package import graph. Now we still fill File-level metadata for such packages while skipping duplicate function-body parsing.
zh(optional):
(Optional) Which issue(s) this PR fixes:
(optional) The PR that updates user documentation: