fix: Session.call throws wrong error type for server errors #112
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.
Resolves FTRACK-98698b84-0f46-424e-a03d-7d92f606d82f
Changes
This PR consists the changes related with
session.call
function's error handling. When response is tried to be decoded and if error has been encountered while doing that, it will match withMalformedResponseError
. Other errors will be already handled bygetErrorFromResponse
until then exceptAbortError
. Since the error has been already handled, error reason can be directly thrown.Test
This flow can be tested with 2FA feature on Studio or Review. However, other
session.call
error cases should be tested.