We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It is a common practice to introduce a generic Exception interface so that all exceptions thrown by this library can be caught in a single catch.
Also, as discussed on gitter, we should create more exceptions instead of one or two big ones.
The text was updated successfully, but these errors were encountered:
👍
At least differentiate between client exceptions (400s), server exceptions (500s) and networking errors (timeouts and such).
Sorry, something went wrong.
That's a good point.
Currently the separation is based on single and multi requests.
Can you open a separate issue for that?
No branches or pull requests
It is a common practice to introduce a generic Exception interface so that all exceptions thrown by this library can be caught in a single catch.
Also, as discussed on gitter, we should create more exceptions instead of one or two big ones.
The text was updated successfully, but these errors were encountered: