Menu
According to the RxJS 5 MIGRATION.md it looks like shareReplay() been removed.
.publishReplay(1).refCount() faithfully replicate the behaviour? Basically I need to replay the single most recent data set to any new subscribers.
769
The shareReplay prevents additional subscribers to the returned observable triggering a new response, but you're creating a new one each time.
In contrast to share , shareReplay exposes a ReplaySubject to subscribers. ReplaySubject(1) is very similar to a BehaviorSubject .
Operatorslink Pipes let you combine multiple functions into a single function. The pipe() function takes as its arguments the functions you want to combine, and returns a new function that, when executed, runs the composed functions in sequence.
Happy news, shareReplay() is back in RxJS 5.4.0:
https://github.com/ReactiveX/rxjs/blob/892700dd4f5d5e5f9ae9276ede32208f4390c5e9/CHANGELOG.md#540-2017-05-09
181
The short answer : Quoting Sir Blesh :
The problem RxJS 5 is trying to solve is that ConnectableObservables should be "reconnectable", and
refCountshould return an observable that is cold until subscribed to, then hot until all subscriptions have ended, then cold again.
The issue is that of the behaviour of subjects after completion which prevents a connectable observable to be reconnected when completed.
The long answer : https://github.com/ReactiveX/RxJS/issues/453
The current API appears to be the result of a compromise between two visions of the reconnection issue. It would be great if those involved could do a summary of the issues at hand. My understanding is that .publishReplay(1).refCount() should keep the old behaviour, that is that when your number of subscribers reaches 0, the source is disconnected, and you can't replay it. But don't take my word for it, test it, I got lost following the discussion.
43
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
