-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: switch to native namespaced packages #9
Conversation
🧪 Test coverage: 94.19% Code Coverage Summary
Diff against main
Results for commit: 8ed90d9 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Trivy scanning results. |
@@ -81,10 +81,15 @@ warn_unused_ignores = false | |||
show_error_codes = true | |||
check_untyped_defs = true | |||
no_implicit_optional = true | |||
mypy_path = ['packages'] | |||
explicit_package_bases = true | |||
mypy_path = [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This isn't ideal (but on the other hand it doesn't seem like a deal breaker) - when you create a new package, you have to add it to the list here, so that mypy can properly recognize it. So far, I haven't found a workaround around this.
No description provided.