Repository navigation
Analyze dynamic imports and release 0.6.0 - #4
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.
Problem and behavior
Dynamic imports previously bypassed the architecture rules. Add non-executing AST analysis for importlib.import_module, importlib.import, built-in import, and imports embedded in literal exec/eval/compile code. Resolved targets feed the existing layer, slice, public API, app/UI and optional wildcard-export checks.
Resolve loader aliases, constants, concatenation, f-strings, joins, relative packages and fromlists. Preserve scope and possible loader bindings across function parameters, methods, comprehensions and branches. A recognized loader with an unresolved target or opaque use fails explicitly with dynamic-imports, so uncertainty no longer counts as successful validation. Nested code expansion and diagnostics have finite budgets.
Release 0.6.0 includes updated documentation and installed-wheel acceptance controls. No new dependencies; project code and user-defined import hooks are never executed.
Validation