Add support for plain string responses in HTTP request handler #53
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
BaseHttpRequestHandler.Send<TResult>method that don't require JSON deserializationTResultis of typestring, the response content is now read directly as a string instead of attempting JSON deserializationChanges
This PR adds an additional condition in the
Send<TResult>method to check iftypeof(TResult) == typeof(string)before falling back to JSON deserialization. This prevents deserialization errors when the API endpoint returns plain text responses.The change follows the existing pattern for handling
HttpResponseMessageresponses and maintains the same coding style.Test plan
🤖 Generated with Claude Code