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

Allow custom response handlers to return nil result values #168

Merged
merged 3 commits into from
May 9, 2024

Conversation

zhangyangjing
Copy link
Contributor

Maintain consistent behavior with the default handler by returning nil for HTTP responses with a status code of 204 or empty body.

Maintain consistent behavior with the default handler by returning nil for HTTP responses with a status code of 204 or empty body.
@zhangyangjing zhangyangjing requested a review from a team as a code owner May 9, 2024 02:27
Copy link
Member

@andrueastman andrueastman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for contribution here @zhangyangjing

Any chance you can also add a changelog entry in the file at the root of the repository with a minor version bump?

nethttp_request_adapter.go Show resolved Hide resolved
Copy link
Member

@baywet baywet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for making the changes!

@baywet
Copy link
Member

baywet commented May 9, 2024

@zhangyangjing can you sign the CLA please? (see the bot comment)

@zhangyangjing
Copy link
Contributor Author

@microsoft-github-policy-service agree

@zhangyangjing zhangyangjing requested a review from andrueastman May 9, 2024 15:33
@baywet baywet merged commit afc0304 into microsoft:main May 9, 2024
7 checks passed
baywet added a commit that referenced this pull request May 9, 2024
Signed-off-by: Vincent Biret <vibiret@microsoft.com>
baywet added a commit that referenced this pull request May 9, 2024
- fixes version bump for merge of #168 and #169
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants