Skip to content

fix: throw generic HTTPError #368

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

Merged
merged 1 commit into from
May 8, 2024
Merged

fix: throw generic HTTPError #368

merged 1 commit into from
May 8, 2024

Conversation

grdsdev
Copy link
Collaborator

@grdsdev grdsdev commented May 7, 2024

What kind of change does this PR introduce?

Fix #324

What is the current behavior?

Request fails to decode non-JSON errors

What is the new behavior?

Fallback to generic HTTPError when no other error can be decoded

Additional context

Add any other context or screenshots.

@grdsdev grdsdev force-pushed the fix/http-error branch 2 times, most recently from e154665 to 5ddd73f Compare May 7, 2024 18:13
@grdsdev grdsdev marked this pull request as draft May 7, 2024 18:23
@grdsdev grdsdev requested a review from dshukertjr May 7, 2024 19:07
@grdsdev grdsdev marked this pull request as ready for review May 7, 2024 19:07
@grdsdev grdsdev merged commit 782e940 into main May 8, 2024
@grdsdev grdsdev deleted the fix/http-error branch May 8, 2024 09:04
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

Successfully merging this pull request may close these issues.

DecodingError when receiving 401 from API
2 participants