override-response-parsing #484
Merged
+69
−4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Summary: - Support override of response type, driving deserialization, even when reponse `Content-Type` header is misleading. - Added robot test `Google AcceleratorTypes Demonstrating Response Content Type Override`.
general-kroll-4-life
force-pushed
the
feature/override-reponse-parsing
branch
from
9469a5b to
3cbabf7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Content-Typeheader is misleading.Google AcceleratorTypes Demonstrating Response Content Type Override.Type of change
Issues referenced.
N/A.
Evidence
Google AcceleratorTypes Demonstrating Response Content Type Override.Checklist:
Variations
N/A.
Tech Debt
No technical debt is added in this change.