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

feat: return a wrapper on Response on UnexpectedResponse #76

Closed
wants to merge 13 commits into from

Conversation

spolu
Copy link
Contributor

@spolu spolu commented Jun 1, 2024

Fixes #75

To give access to body bytes to let the user parse the response body for API errors when status code is not 200.

Package it as a wrapper to prevent interference across hyper versions

@spolu spolu requested a review from a team June 1, 2024 10:33
@spolu spolu changed the title feat: return Response<body> on UnexpectedResponse feat: return a wrapper on Response on UnexpectedResponse to allow access to Body bytes Jun 3, 2024
@spolu spolu changed the title feat: return a wrapper on Response on UnexpectedResponse to allow access to Body bytes feat: return a wrapper on Response on UnexpectedResponse Jun 3, 2024
@keelerm84
Copy link
Member

I am sorry for the delay in responding to this PR. I have some things I need to wrap up early this week, but I will try to take a look before the end of the week.

@keelerm84
Copy link
Member

@spolu thank you for your patience with this. I had originally planned on getting back to this sooner than this, but several things came up and required my attention.

Both you and another developer have contributed PRs providing some similar behavior. I have merged your work, along with theirs, into a new PR (#79) and included some adjustments we would also like to make.

I'm going to close this PR and keep all communication focused on that new PR.

Once again, thank you for your contribution and I look forward to hearing if this new PR works for you.

@keelerm84 keelerm84 closed this Jul 26, 2024
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.

Ability to get the body when status code != 200
3 participants