-
Notifications
You must be signed in to change notification settings - Fork 2.6k
chore: Part 1 of adding type validation to tests - type checking test/core/pipeline/ folder
#10409
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
|
|
||
| name: str | ||
| type: type | ||
| type: type | UnionType |
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.
Only change needed outside of test folder. Without this then passing something like type=int | str would cause mypy to throw an error.
|
I see there's a type error. (Over time, let's also check if mypy running time increases significantly) |
@anakin87 I'll need to investigate this more about how we can properly support this. I'm not too familiar with how python treats |
|
@anakin87 I resolved the typing issues so this should be good to go now! |
anakin87
left a comment
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.
Looks good! (Sorry for the conflicts)
Pull Request Test Coverage Report for Build 21248149201Details
💛 - Coveralls |
Related Issues
Proposed Changes:
Add type checking to the
test/core/pipeline/folder.How did you test it?
Running typing tests on the newly added folder.
Notes for the reviewer
Checklist
fix:,feat:,build:,chore:,ci:,docs:,style:,refactor:,perf:,test:and added!in case the PR includes breaking changes.