Add Type hints to the codebase

[leandrodesouzadev]

Is there any plans to add type hints to the codebase?
As a newcomer to the project, i feel like there's a lot of places that could use type hints to better describe functions.
I'm willing to do the job! 🦾

[tim-schilling]

I don't have major any qualms against it. I think they're useful for method signatures and class members. However, I'm not committing getting to a point where we are going to say we need type hints on everything.

[tim-schilling]

@leandrodesouzadev looks like you have the go-ahead on this. I'd suggest doing it piecemeal so you don't end up with too many merge conflicts from long living branches. And so you don't burn yourself out. Thank you!

[leandrodesouzadev]

Looks great, baby steps all the way.
Maybe one module per pull request? How that sounds to you?
Monday I will start working on this.

[tim-schilling]

That sounds good! Let us know if you need any help.

[tim-schilling]

@leandrodesouzadev circling back to this. How are things going?

[leandrodesouzadev]

I haven't touched on the code base for a while now.
I will try to do some other module or two this week and open the pull requests

[ataylor32]

I would like to see this addressed too. Currently, I'm getting this error with mypy:

error: Skipping analyzing "debug_toolbar": module is installed, but missing library stubs or py.typed marker  [import-untyped]

[tim-schilling]

@ataylor32 is this something you would have time to help out with?

[ataylor32]

@tim-schilling Possibly, but I don't have experience with creating stubs. I'll have to look into it.