You could probably use a combination `share` and `buffer` to get that behavior, but I'd honestly jus...

# rx

[alexsullivan114]

You could probably use a combination share and buffer to get that behavior, but I'd honestly just go the behavior subject route.

[iex]

Hmm but that makes things more verbose. Why would I prefer it (if it's possible using those operators)?

[iex]

though the behavior subject can be called with startWith(observable) or something like that, right?

[alexsullivan114]

It's an observable so you can use all of the normal operators

[alexsullivan114]

I think the share + buffer route (and I'm not sure that would actually work) will be more verbose and require more cognitive load to reason through

[alexsullivan114]

BehaviorSubject is very very simple and one line to declare, and one extra line to expose hidden.

[alexsullivan114]

share + replay is probably what you actually want if you're going the observable route

[Zach Klippenstein (he/him) [MOD]]

share probably doesn't make sense with replay, they're both multicasting operators (share is just publish().refCount()). You want just replay(1) and then either refCount, autoConnect, or to just call connect yourself on the returned ConnectableObservable.

[iex]

awesome, thanks!

[trevjones]

https://github.com/JakeWharton/RxReplayingShare