chore: remove pyright configuration and use ty instead - #132
Merged
Conversation
Contributor
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
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.
Removes all pyright configuration files and references since the project has migrated to using
tyfor type checking.Changes
pyrightconfig.json(pyright-specific config file).pre-commit-config.yaml(lines 36-40).github/workflows/test-coverage.ymlRationale
The project now uses
ty(the new strict type checker) as the primary type checking tool. Pyright was previously used but is no longer needed since:[tool.ty]configuration is already inpyproject.tomlType Checking Pipeline
The workflow now uses:
Instead of:
Testing
✅ All 231 tests pass
✅ Pre-commit hooks pass
✅ No functional changes, only configuration cleanup
Notes
continue-on-error: trueflag is kept so CI doesn't fail on type warnings