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

client: enable configuration of client response interface #250

Merged
merged 1 commit into from Oct 14, 2022

Conversation

Kunde21
Copy link
Contributor

@Kunde21 Kunde21 commented Jul 3, 2022

Default ClientResponse implementation locks down access to the raw
response, which causes difficulty in debugging outside of debug logs.

Opening up the configuation gives flexibility to those that need it,
while keeping the default for backwards compatability. Current users
will not need to make any changes.

Signed-off-by: Chad Kunde Kunde21@gmail.com

Default ClientResponse implementation locks down access to the raw
response, which causes difficulty in debugging outside of debug logs.

Opening up the configuation gives flexibility to those that need it,
while keeping the default for backwards compatability.  Current users
will not need to make any changes.

Signed-off-by: Chad Kunde <Kunde21@gmail.com>
@Kunde21
Copy link
Contributor Author

Kunde21 commented Jul 15, 2022

Fixes #240

@casualjim casualjim merged commit c12369b into go-openapi:master Oct 14, 2022
@casualjim
Copy link
Member

Sorry I missed this PR for a long time. If you have more in the future feel free to ping me in slack if I don't notice it.

@Kunde21 Kunde21 deleted the custom_clientresponse branch October 23, 2022 11:34
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.

None yet

2 participants