fix: correct ArtifactRef import path and UI module dependencies - #10
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.
Summary
Fixes two import bugs that cause ModuleNotFoundError:
ArtifactReflazy import pointed to non-existentdevqubit_engine.core.modelsinstead ofdevqubit_engine.core.typesdevqubit-uiimported fromdevqubitmetapackage instead ofdevqubit_enginedirectly, breaking standalone UI installationType of change
Changelog (user-facing only)
changelog.d/Checklist
uv run pre-commit run --all-files)uv run pytest)uv.lock(uv lock) and committed itNotes for reviewers
No breaking changes - these are pure bug fixes. The UI now imports directly from
devqubit_enginesubmodules, which avoids potential circular dependency issues.