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

Propagate isNetworkError through error wrappers #3620

Merged
merged 3 commits into from
Apr 5, 2022
Merged

Conversation

goto-bus-stop
Copy link
Contributor

The ErrorWithCause class uses the same signature as the builtin Error
does, but it supports the { cause } option in older environments, and
it propagates the isNetworkError property from the underlying error.

The `ErrorWithCause` class uses the same signature as the builtin Error
does, but it supports the `{ cause }` option in older environments, and
it propagates the `isNetworkError` property from the underlying error.
@aduh95 aduh95 merged commit b22a812 into main Apr 5, 2022
@aduh95 aduh95 deleted the propagate-network-error branch April 5, 2022 13:57
@github-actions github-actions bot mentioned this pull request Apr 7, 2022
github-actions bot added a commit that referenced this pull request Apr 7, 2022
| Package                | Version | Package                | Version |
| ---------------------- | ------- | ---------------------- | ------- |
| @uppy/aws-s3           |   2.0.9 | @uppy/utils            |   4.0.6 |
| @uppy/companion-client |   2.0.6 | @uppy/robodog          |   2.5.2 |
| @uppy/compressor       |   0.2.4 | uppy                   |   2.9.2 |
| @uppy/transloadit      |   2.1.4 |                        |         |

- @uppy/aws-s3,@uppy/companion-client,@uppy/transloadit,@uppy/utils: Propagate `isNetworkError` through error wrappers (Renée Kooi / #3620)
- @uppy/compressor: Merge new name and type into compressed file (Camilo Forero / #3606)
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.

None yet

3 participants