Closed LiquidPL closed 2 years ago
Previously this exception would always have 0 as the status code, making it impossible to know what was the status of the response that caused that exception.
0
@LiquidPL can you please rebase your branch and fix conflicts. thank you
@mstefan21 Sorry I had to remake the pull request, it's now on PR #53.
Released new version v5.1.0
Previously this exception would always have
0
as the status code, making it impossible to know what was the status of the response that caused that exception.