fix(openapi-fetch): treat default response as error #1139
Merged
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.
Changes
response.default
was simply ignored. Instead, treat it as an error.While some may disagree—technically it can be either—in my observation this is how most people use it since its purpose is handling unexpected HTTP codes (aka exceptions aka errors).
At any rate, interpreting
default
as something rather than ignoring it is an improvement.How to Review
Tests added; CI should pass
Checklist
examples/
directory updated (only applicable for openapi-typescript)