fix(http)!: throw correct error in jsonSelector #2196
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.
Why
This pull request introduces a fix to the
jsonSelector
function in the@equinor/fusion-framework-module-http
package.The current behavior is that the
jsonSelector
function was not properly checking the error type in thecatch
block. This led to always throwing a parser error, even when the correct error was in thecause
property of theHttpJsonResponseError
.The new behavior is that the
jsonSelector
function now correctly checks if the error is an instance ofHttpJsonResponseError
, and then properly handles the error data and cause. This ensures that developers who have caught the error and assumed thecause
property would give the proper error data, will now receive the correct information.This change might introduce breaking changes:
If for some reason developers has catched the error and assumed the
cause
property would give the proper error data, this will no longer be the case.Check off the following: