Skip to content
New issue

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

Suggestion for Error Handling #18

Open
straticsryan opened this issue Jul 19, 2015 · 0 comments
Open

Suggestion for Error Handling #18

straticsryan opened this issue Jul 19, 2015 · 0 comments

Comments

@straticsryan
Copy link

Hey,

Currently, if a channel has gone away and we attempt to send an action for that channel it'll throw a requests.exceptions.HTTPError (404).

That's fine and I understand why that is thrown. However, it would be nice to have the ari client catch the raw HTTPErrors and have its own exceptions (ari.exceptions).

This way, when using the client, we can catch exceptions like ari.exceptions.ChannelNotFoundException or however you want to name it and not have to catch the underlying requests.exceptions.

Ryan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant