Repository navigation
feat: integrate bounded backend-to-schema import lineage - #30
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 integration of PR #21
Extend newly merged API-to-module static import topology on
mainwith one additional bounded import hop and source declaration edges to the Drizzle schema.Added
STATIC_IMPORTSfrom modules to other checked modules andDECLARES_TABLE_CANDIDATEfrom a discovered schema module to syntax-only Drizzle declarations.Limits
An import is not a query and a table candidate is not a deployed table. No actual SQL analysis, runtime telemetry, or production infrastructure is accessed.
Merge gate
Only if fresh Python 3.11/3.13 Validator and real read-only repo.ing smoke succeed; squash merge onto current main, not the old PR stack.