Snippet

Advanced Observable Multicasting with share()

The share() operator is often used too simply. By configuring the connector and reset policies, you can control exactly how a stream is cached (e.g., using ReplaySubject) and when the underlying producer should be torn down or restarted.

snippet.js

javascript

const shared$ = source$.pipe(
  share({
    connector: () => new ReplaySubject(1),
    resetOnComplete: false,
    resetOnError: false,
    resetOnRefCountZero: true
  })
);

angular

Breakdown

connector: () => new ReplaySubject(1)

Defines the internal subject used to multicast values, in this case caching the last emitted value.

resetOnRefCountZero: true

Ensures the source is unsubscribed when all observers disconnect, saving resources in complex SPAs.

Previous snippet Next snippet

More Expert JavaScript exercises →

Advanced Observable Multicasting with share()

Related