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

forkJoin/combineLatest works differently from 6.6.2 to 6.6.3 #7517

Open
dmcliver opened this issue Nov 21, 2024 · 0 comments
Open

forkJoin/combineLatest works differently from 6.6.2 to 6.6.3 #7517

dmcliver opened this issue Nov 21, 2024 · 0 comments

Comments

@dmcliver
Copy link

Describe the bug

forkJoin/combineLatest works differently from 6.6.2 to 6.6.3 when used with a ReplaySubject and Observable, the replay subject doesn't seem to emit the next value.

Expected behavior

From the reproduction URL provided below

Expected console output (as seen in rxjs <= 6.6.2):
0:one
1:two

Actual console output (as seen in rxjs >= 6.6.3):
0:one
0:two

I thought combineLatest might solve this issue instead, but even using combineLatest also doesn't make any difference

Reproduction code

No response

Reproduction URL

https://stackblitz.com/edit/rxjs-7dw9nv?file=index.ts,package.json

Version

6.6.3

Environment

Angular CLI: 16.2.12
Node: 18.20.2
Package Manager: npm 10.5.0
OS: win32 x64

Angular: 16.2.12
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, localize, platform-browser
... platform-browser-dynamic, router

Package Version

@angular-devkit/architect 0.1602.12
@angular-devkit/build-angular 16.2.12
@angular-devkit/core 16.2.12
@angular-devkit/schematics 16.2.12
@angular/cdk 16.2.14
@angular/flex-layout 15.0.0-beta.42
@angular/material 16.2.14
@angular/material-moment-adapter 16.2.14
@schematics/angular 16.2.12
rxjs 7.8.1
typescript 4.9.5
zone.js 0.13.3

Additional context

I cant find anyone mentioning this problem from an internet search but as 7.8.1 is two years old it would strike me as odd that if this is a bug no one else has discovered it. So perhaps it's just a case of incorrect usage of the library?

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

No branches or pull requests

1 participant