This repository has been archived by the owner on May 3, 2022. It is now read-only.
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.
The
<verb>Json
helper methods throw an Error when the server responds with a non-zero status code. They also attach the status code and result as properties.This, however, is not compatible with TypeScript strict type checking. As a result, code depending on
http-client
that use strict type checking (such asactions/toolkit
) can't read the status code and result properties without resorting to TypeScript hacks, such as casting the error object toany
and ignoring the resulting lint warnings.This PR adds a new error subclass,
HttpClientError
, which properties to store the status code and result. Throwing a different error type also lets callers distinguish between errors related to the API call from other generic errors, such as socket errors.