Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: show underlying errors in fetch / xhr #13687

Merged

Conversation

joon-won
Copy link
Member

@joon-won joon-won commented Aug 7, 2024

Description of changes

Modify error type in fetchtransfer, xhrhandler to show underlying errors in ApiError.underlyingError and StorageError/underlyingError respectively.

Issue #, if available

Description of how you validated changes

Checklist

  • PR description included
  • yarn test passes
  • Unit Tests are changed or added
  • Relevant documentation is changed or added (and PR referenced)

Checklist for repo maintainers

  • Verify E2E tests for existing workflows are working as expected or add E2E tests for newly added workflows
  • New source file paths included in this PR have been added to CODEOWNERS, if appropriate

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@joon-won joon-won changed the title chore: modify fetchtransfer and xhrtransfer error handler to show underlying errors chore: show underlying errors in fetch / xhr Aug 7, 2024
@joon-won joon-won requested a review from a team as a code owner August 8, 2024 16:41
AllanZhengYP
AllanZhengYP previously approved these changes Aug 9, 2024
Copy link
Member

@AllanZhengYP AllanZhengYP left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @joon-won for addressing all the comments!

@joon-won joon-won merged commit 5224dc2 into aws-amplify:main Aug 19, 2024
30 checks passed
@joon-won joon-won deleted the joonwonc/chore-surface-fetch-errors branch August 19, 2024 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants