You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Static type checking dramatically reduces developer errors. You've already created types, adding compatibility to PEP 561 would allow us to use static checkers
Possible Implementation
See above
Other information
Am I missing anything? Another way to run a static type checker perhaps?
The text was updated successfully, but these errors were encountered:
👋 This is probably better posted in our Community Forum as it doesn't sound like an issue with the SDK. if it's still an issue for you feel free to post there and a Community member can assist.
I'm actually looking into something for our CI system actually this week (a bunch of different things actually). I'm evaluating a bunch of different options at the moment and this is one of them.
It's going to take some time so I don't have an ETA on it, but I'm hoping by the end of June at the latest. Most likely it'll be sooner.
Proposed changes
I'm new to python so excuse me if I'm missing something obvious.
You've carefully added type hints to the SDK, amazing. When I add a static type checker to my project, like mypy, it can't seem to find them. According to mypy's documentation, packages are supposed to declare their compatibility with a py.typed file in the package directory. See here: https://mypy.readthedocs.io/en/stable/installed_packages.html#creating-pep-561-compatible-packages
Context
Static type checking dramatically reduces developer errors. You've already created types, adding compatibility to PEP 561 would allow us to use static checkers
Possible Implementation
See above
Other information
Am I missing anything? Another way to run a static type checker perhaps?
The text was updated successfully, but these errors were encountered: