-
Notifications
You must be signed in to change notification settings - Fork 3
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
Use a stricter configuration for basedpyright #332
base: main
Are you sure you want to change the base?
Conversation
ccc29b0
to
45c4b47
Compare
bfbdfb6
to
66c989c
Compare
This also modifies the diagnositic behavior for various circumstances. This currently leaves all of the rules that would cause errors explicitly disabled, while leaving everything else enabled. Over time, the rules which were disabled for this reason will be re-enabled and the corresponding issues will be fixed in future commits.
2a350b8
to
347dd59
Compare
Note: Unknown type reporting is currently disabled, there is a comment in Note 2: I've added some TODO comments into the code-base, which were not actually resolved here. That's because these TODOs are completely unrelated to this PR and are essentially just issues that I've noticed while working on this. These should be fixed in another PR(s) some time in the future. |
A type checker that isn't strict is a bad type checker
This will likely break all PRs :P
main
, you might want to do a propergit merge
as opposed togit rebase
, so that you can bring your code up-to-date with these changes in that merge commit, rather than having to edit each commit in a rebase to be compatible. (Unless you only have 1-2 commits)