Repository navigation
feat: integrate source-backed API-to-module imports cleanly - #29
Merged
Merged
Conversation
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.
Clean import-topology integration from PR #20
Ports only the tested import parser changes onto current
main, now that API/schema discovery is merged through PR #28.Included
STATIC_IMPORTScandidate relations with source lines and evidence hashes.Limits
Regex source syntax is not an AST proof or runtime call graph, dynamic/multiline imports remain unassessed, and no production telemetry/DB access is introduced. No hosted deployment.
Merge gate
Fresh Python 3.11/3.13 and real repo.ing source smoke; only squash-merge after green checks. Earlier stacked draft #20 will remain superseded by this integration.