mypy linting and type checking#26
Conversation
|
@Samira-El and @koszti - This is ready for review! 🚀 😄 Link to CI jobs on my fork: |
|
Hey Aaron, thanks for the PR. Don't know why CI in your branch is passing ?!🤔 |
|
Also, can you remove the |
Done! ✅ Sorry that creeped in. 👻 |
Not sure about this... could be version differences or something else going on... |
|
@aaronsteers I'm seeing the same errors on a fresh clone and install of your branch |
|
Running fixed all but one error |
Nice! Thanks, @edgarrmondragon! Perhaps when I was running locally via poetry the I think the last one is new since I last touched this. Looks like its related to the requests library. UPDATE: I made a quick attempt to resolve both issues in this commit: 0825e01 |
aaronsteers
left a comment
There was a problem hiding this comment.
Per @edgarrmondragon's comment. 👍
|
I had to make this change: d67ad2e for the CI jobs to run on this PR. |
|
Looks like Unify is unhappy, we've recently added a linting step to check that only single quotes are used for consistency reasons. |
|
Mypy isn't happy too: |

Adding mypy checks and type hints.
I intentionally used
Anyon types if I was not sure of the expected type myself.Tests are passing locally but for some reason I'm not getting them to run in CI. I'll check on that and post back.