Add a CI check for type safety check #16
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
natemort
approved these changes
Aug 27, 2025
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.
What changed?
Add a CI check for type safety check. This pr only add the check and does not enable it. Enable the check will come in a later PR with also fixing type safety in current code.
Why?
Python is not type-safe by default, which can lead to runtime errors that could be caught at development time. By adding type checking to our CI pipeline, we can catch type-related issues early and improve code quality. This is especially important for a client library where type safety helps users catch errors before they reach production.
How did you test it?
run
uv tool run mypy cadence/Potential risks
Release notes
Documentation Changes