- Notifications
You must be signed in to change notification settings - Fork673
fix: argument type was not a tuple as expected#1399
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
fix: argument type was not a tuple as expected#1399
Uh oh!
There was an error while loading.Please reload this page.
Conversation
While adding type-hints mypy flagged this as an issue. The thirdargument to register_custom_action is supposed to be a tuple. It wasbeing passed as a string rather than a tuple of strings.
codecov-commenter commentedApr 18, 2021
Codecov Report
@@ Coverage Diff @@## master #1399 +/- ##======================================= Coverage 80.16% 80.16% ======================================= Files 73 73 Lines 4073 4073 ======================================= Hits 3265 3265 Misses 808 808
Flags with carried forward coverage won't be shown.Click here to find out more.
Continue to review full report at Codecov.
|
That mistake happens too often in Python 😄 LGTM 👍 |
One of the things I like with adding the static type-hints and then using mypy. That is how I caught this one. May find more issues as more and more type-hints are added. |
While adding type-hints mypy flagged this as an issue. The third
argument to register_custom_action is supposed to be a tuple. It was
being passed as a string rather than a tuple of strings.