fix: do not throw unhandled exception when data is undefined in interceptor.reply #4036
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.
This relates to...
N/A
Rationale
See below (Bug Fixes)
Changes
See below (Bug Fixes)
Features
N/A
Bug Fixes
When interceptor.reply would return
{ data: undefined }
, it blows up ingetResponseData
:This got introduced here, more specifcally, this change
More specifically, in the before and after, data is not the same when it was undefined originally:
vs
As previously, when data was undefined,
''
would be passed togetResponseData
, andgetResponseData
would return''
, I ensured we now also return''
whendata
being passed togetResponseData
isundefined
.Breaking Changes and Deprecations
N/A
Status