-
Notifications
You must be signed in to change notification settings - Fork 34
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
Untyped decorator issue with rich-click #85
Comments
I'm not a big mypy user (as in, I've not used it and don't use it) so this isn't a fix that comes easily to me. If you're able to put in a PR to solve the issue, that would be great 🙏🏻 Thanks! |
Sure, will give it a try! |
All typing issues should have hopefully been resolved with #126, and will be released in 1.7. All rich-click decorators will now have full typing parity with click 8.x, meaning if a static type check works in click 8.x then it should also work in rich-click 1.7. This particular static type checking failure was easy to reproduce on my end, and I have confirmed it has been resolved subsequent to the code changes in #126. |
Great, thank you. I will give it a try! |
Click used to have this issue with static type checker:
They addressed this issue but when I switched to using
rich-click
, I am getting this error message again when runningmypy
.The text was updated successfully, but these errors were encountered: