Repository navigation
fix: resolve typesense imports in mypy and fix the type errors it surfaces - #152
Merged
Merged
Conversation
tharropoulos
force-pushed
the
fix/mypy-module-path
branch
from
October 6, 2026 11:28
5840ac3 to
99fa27b
Compare
tharropoulos
force-pushed
the
fix/mypy-module-path
branch
2 times, most recently
from
October 7, 2026 10:10
2a44ac4 to
94590e2
Compare
tharropoulos
force-pushed
the
fix/mypy-module-path
branch
from
October 7, 2026 10:12
94590e2 to
977e8e2
Compare
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
2 participants
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.
typesense.*import asAny(nomypy_path = src), so cross-module types were never checked; this turns that on and fixes the errors it surfaces