Fixed mypy errors

3.1.3

fixed code v2

Minor update: Added stubbings

Now mypy won't complain about the library missing stubbings...hopefully !

Architecture Overhaul + Improvements

So I updated the code to improve the architecture and migrated to poetry from Pipenv.

I had to do this to benefit from the build system of poetry and remove all the boilerplate coming from something like "setup.py"

v3.0.3 - Added missing features

As the title says, I added the missing features from the last release to the code.

BREAKING CHANGE - OVERHAUL

I had to updated the whole code structure to make things easier for me to develop + maintain and hopefully future-proof

• Divided the Client into many sub Endpoints as sub classes, now you only have to import the class you really need without having to import the whole library at once !
• Added error checking and type safety thanks to python's type hinting! Please activate type checking on vs code to get the benefits.
• REMOVED THROWING FROM THE WHOLE LIBRARY !! No more try: ... raise ! Errors are returned as ApiError class, so you can simply run if isinstance(res, ApiError) and check without worrying about the method you're calling throwing any errors. This is the best course of action as we need as little unexpected behavior as possible. Runtime errors are a big no no so I had to make sure everything goes correctly!.

Just some small code upgrades

Nothing to add here, just a version bump.

v2 asynchronous

The v2 is the upgrade I made of the original project.

Modified the library to make it asynchronous by default using httpx.