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

HTTP Client Error Handling. #34

Closed
cfrademan opened this Issue May 13, 2018 · 1 comment

Comments

1 participant
@cfrademan
Member

cfrademan commented May 13, 2018

Parse HTTP Error codes and raise exceptions.
Try to parse json error response.

@cfrademan cfrademan self-assigned this May 13, 2018

@cfrademan cfrademan added this to To Do in Beta/First Release via automation May 13, 2018

@cfrademan cfrademan added this to To Do in API Clients via automation May 13, 2018

@cfrademan cfrademan moved this from To Do to In Progress in Beta/First Release May 13, 2018

@cfrademan cfrademan changed the title from HTTP Client. to HTTP Client Error Handling. May 13, 2018

@cfrademan cfrademan moved this from To Do to In Progress in API Clients May 13, 2018

cfrademan added a commit to cfrademan/luxon that referenced this issue May 14, 2018

HTTP Client Error Handling. TachyonicProject#34
Added new exceptions for HTTP Error Handling in client.

If Status > 400 returned raises HTTPError with corresponding error.

If response in body contains json error message, then use that to raise.

cfrademan added a commit that referenced this issue May 14, 2018

Merge pull request #39 from cfrademan/development
HTTP Client Error Handling. #34

cfrademan added a commit that referenced this issue May 14, 2018

@cfrademan

This comment has been minimized.

Member

cfrademan commented May 14, 2018

Error handling added and tested.

@cfrademan cfrademan closed this May 14, 2018

Beta/First Release automation moved this from In Progress to Completed May 14, 2018

API Clients automation moved this from In Progress to Completed May 14, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment