You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
forkJoin/combineLatest works differently from 6.6.2 to 6.6.3 and even latest version 7.8.1 #7517
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
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?
changed the title [-]forkJoin/combineLatest works differently from 6.6.2 to 6.6.3[/-][+]forkJoin/combineLatest works differently from 6.6.2 to 6.6.3 and even latest version 7.8.1[/+]on Dec 4, 2024
Yes, caused by commit 47d9e33. ReplaySubject behaviour changed, now it satisfies the should not buffer nexted values after complete unit test. forkJoin/combineLatest work as they used to.
Activity
[-]forkJoin/combineLatest works differently from 6.6.2 to 6.6.3[/-][+]forkJoin/combineLatest works differently from 6.6.2 to 6.6.3 and even latest version 7.8.1[/+]dmcliver commentedon Dec 4, 2024
Possibly caused by
47d9e33#diff-a287f66fc20bf26caa2f42935756aa6a094f400e91d6b4a388aee4e4e11675c4R38
@cartant ?
netoctone commentedon Apr 17, 2025
Yes, caused by commit 47d9e33.
ReplaySubjectbehaviour changed, now it satisfies theshould not buffer nexted values after completeunit test.forkJoin/combineLatestwork as they used to.