Conversation
ozsivanov
reviewed
Mar 24, 2021
| } | ||
| if (response.statusCode) { | ||
| error.statusCode = response.statusCode; | ||
| if (!error.hasOwnProperty('message')) { |
There was a problem hiding this comment.
Hi @Tranced, I think we may want to also check typeof response.body === 'string' to make sure we're returning a string. It's also worth considering adding an else clause in case response.body isn't a string, and just responding with a generic error message.
Contributor
Author
There was a problem hiding this comment.
Sounds good to me! I'm not sure what cases we'll run into if the error message is not a string. So, in that case, I'll just leave it with the current default behavior.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Just wanted to pass along the error message generically in our SDK if customers come upon them.
Looks like we only pass status code.
For context, a customer is using native auth and is only seeing a 401.
However, in our authentication example(which just uses a regular request/not the SDK), we're able to see the full stack trace.
Before, the message from the SDK was:
now it's:
License
I confirm that this contribution is made under the terms of the MIT license and that I have the authority necessary to make this contribution on behalf of its copyright owner.