ci: type checking setup (mypy) #3
Merged
Conversation
This file contains 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
A hatch-based environment (`types`) is added. Locally, hatch users can run ``` hatch run types:check ``` to get the checked out code type-checked. Additionally, two workflows are added that test for typing issues. One (`mypy-pr`) only tests files that changed in a PR. The other (`mypy-project`) tests all code. The rational for having two separate tests is that individual PRs should not be blocked by typing issues that appear in the rest of the code base. This can happen when changes are forced into the mainline, or conditions change between (Python) versions.
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.
A hatch-based environment (
types) is added.Locally, hatch users can run
to get the checked out code type-checked.
Additionally, two workflows are added that test for typing issues. One (
mypy-pr) only tests files that changed in a PR. The other (mypy-project) tests all code. The rational for having two separate tests is that individual PRs should not be blocked by typing issues that appear in the rest of the code base. This can happen when changes are forced into the mainline, or conditions change between (Python) versions.