@vercel/blob - Return more useful error message when retrieveClientToken throws custom error message #489
+12
−2
Conversation
This file contains 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
|
|
@daryl-cecile is attempting to deploy a commit to the Curated Tests Team on Vercel. A member of the Team first needs to authorize it. |
Updated response error handling to attempt to extract error message from body.
daryl-cecile
force-pushed
the
feature/custom-error-message-in-retrieveClientToken
branch
from
afb709e
to
252328a
Compare
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.
Updated response error handling to attempt to extract error message from body. It seems the blob package is already set up to receive the error messages of errors thrown in the
retrieveClientToken, so this PR attempts to read this message before falling back to theFailed to retrieve the client tokenmessage.Attempts to fix #488