Early completions of switchMap()

[matthewwithanm]

We use switchMap() a lot, but recently @shushz raised the point that, most of the time, we actually don't want its completion semantics. Whereas switchMap() completes when both the inner and outer observable do, we often want it to complete as soon as the outer one does (similar to error propagation).

As a use case, consider the old typeahead example where you have an observable of strings ("A") that get switchMapped to a http request. It seems natural to have A complete when, for example, the input field is removed from the document, but that doesn't give the most desirable behavior (cancelling the request). The behavior you want would actually be something like:

const smap = (a, proj) => a
  .materialize()
  .switchMap(x => x.kind === 'N'
    ? proj(x.value).materialize().filter(n => n.kind !== 'C')
    : Observable.of(x)
  )
  .dematerialize();

or maybe something with .switchMap(...).takeUntil(...).

So now we're wondering

1. Are we abusing observable completion?
2. Is this behavior generally more desirable than the current behavior or are we just in a bubble?
3. Is this behavior desirable often enough that it should be easier to do (correctly) with Rx?

or maybe we're just missing something obvious?

cc @hansonw @trxcllnt
Somewhat related: #1815

[trxcllnt]

@matthewwithanm does this work?

source.publish((xs) => xs
    .switchMap(project)
    .takeUntil(xs.lastOrDefault(0)))

[matthewwithanm]

Hey @trxcllnt! lastOrDefault() isn't in RxJS anymore, right? But yeah, that's the general idea.

[paulpdaniels]

use .takeLast(1).defaultIfEmpty(0) instead.

[matthewwithanm]

Thanks @paulpdaniels! I understood @trxcllnt's response but I was really looking for answers to the questions in the OP—especially 2. I'm assuming your answer to (3) is that combining these five operators (publish(), switchMap(), takeUntil(), takeLast(), and defaultIfEmpty()) is obvious/clear/easy enough?

[benlesh]

Closing as stale.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.