Closed emontnemery closed 8 months ago
Is this a breaking change for users of the library?
What's the reason for that goal?
callback functions to accept a bool status and an optional response
Thanks Martin, the PR has been updated with this information
I fixed a typo.
Breaking change
Most user facing functions accepting an optional callback function have been changed such that the optional arguments are now kwarg only
Change
Make optional callback functions kwarg only
Background
This is the first step in refactoring the callback functions to accept a bool status and an optional response.
Refactoring the callback handling is needed because callbacks are currently only called if the request suceeds; there's no call if the request fails. This means any user relying on callbacks will hang forever or until a timeout when the request fails.