fix: Add raw_response
parameter support for request sending
#124
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.
Why:
Adds support for returning raw endpoint response data thus giving developers the option to bypass model validation if needed. Mandating model validation by default without a way to disable it limits flexibility and doesn't align with best practices in software design.
What:
raw_response
flag in the request method.raw_response
functionality for JSON and text content types.How can it be used:
To retrieve unprocessed response data from a request, set the
raw_response
parameter toTrue
:How did you test it:
Unit tests were created to assert correct behavior of the
raw_response
functionality, including:raw_response
is set toTrue
.raw_response
isFalse
.Notes for the reviewer:
Ensure the new tests correctly distinguish between parsed and unparsed behavior of the response. Pay attention to the handling of different content types within the tests.