-
Notifications
You must be signed in to change notification settings - Fork 74
MyPy Typechecking #19
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
Comments
Yeh go for it 👍 |
Something that I noticed when walking through the code: There's a lot of untyped Example:
The downside of TypedDict is that it's a 3.8+ feature, and some functionality requires This is out of scope for what I intend, though. |
@chrisjsewell Which test failures should I expect? |
Which test failures should I expect? None? FYI in-terma of mypy, you could just try add the pre-commit hook to the pre-commit config file, then fix the code accordingly: https://github.com/pre-commit/mirrors-mypy |
Ah, sorry. I got a bug I introduced locally mixed up with some of the skipped tests. Right now, there's around ~70 standing errors that I still need to fix, after grabbing the lowest hanging fruit, so I'll need to figure something out before adding a pre-commit hook. |
Yeh no worries. The only thing to bear in mind is that we "shouldn't" (without very good reason) change the code in any way that deviates from the source markdown-it API. Also I am definitely +1 for |
As part of getting to learning how to hack on the package, I've started running MyPy for a "guided tour" of the API.
Do you mind if I send in one or more PRs to fix/silence some of the warnings?
The text was updated successfully, but these errors were encountered: