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.

Sign up for GitHub

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

Jump to bottom

fix(forkJoin): the first empty source will now cause an EmptyError #7266

Merged
merged 1 commit into from
May 25, 2023
Merged

fix(forkJoin): the first empty source will now cause an EmptyError #7266

merged 1 commit into from
May 25, 2023

Commits on May 25, 2023

  1. fix(forkJoin): the first empty source will now cause an EmptyError 

    BREAKING CHANGE: `forkJoin` will no longer just complete if a source completes without a value. Instead you will get an error of `EmptyError`. If you want to complete in this case, add `catchError(() => EMPTY)` to the forkJoin... however, if you just want to default the sources of your `forkJoin` to some other value if they're empty, apply the `defaultIfEmpty` operator. for example, `forkJoin(sources.map(defaultIfEmpty(null)))`.

resolves ReactiveX#5561
    @benlesh
    benlesh committed May 25, 2023
    Configuration menu
    Copy the full SHA
    82184b2 View commit details
    Browse the repository at this point in the history