Tests asserting unsubscription chains don't break

[staltz]

We need to add tests that each operator propagates unsubscription from the destination to the source.

Here is an example:

  it('should not break unsubscription chain when unsubscribed explicitly', function () {
    var e1 =     hot('--a--b--c--d--e----|');
    var unsub =      '         !          ';
    var e1subs =     '^        !          ';
    var skip =   hot('-------------x--|   ');
    var skipSubs =   '^        !          ';
    var expected =  ('----------          ');

    var result = e1
      .mergeMap(function (x) { return Observable.of(x); })
      .skipUntil(skip)
      .mergeMap(function (x) { return Observable.of(x); });

    expectObservable(result, unsub).toBe(expected);
    expectSubscriptions(e1.subscriptions).toBe(e1subs);
    expectSubscriptions(skip.subscriptions).toBe(skipSubs);
  });

Notice the use of the mergeMap sandwich there.

---

• buffer
• bufferCount
• bufferTime
• bufferToggle
• bufferWhen
• catch
• combineAll
• combineLatest
• concat-static
• concat
• concatAll
• concatMap
• concatMapTo
• count
• debounce
• debounceTime
• defaultIfEmpty
• delay
• dematerialize
• distinctUntilChanged
• distinctUntilKeyChanged
• do
• elementAt
• every
• exhaust
• exhaustMap
• expand
• filter
• find
• findIndex
• first
• groupBy
• ignoreElements
• isEmpty
• last
• map
• mapTo
• materialize
• max
• merge-static
• merge
• mergeAll
• mergeMap
• mergeMapTo
• mergeScan
• min
• multicast
• observeOn
• partition
• publish
• publishBehavior
• publishLast
• publishReplay
• reduce
• repeat
• retry
• retryWhen
• sample
• sampleTime
• scan
• share
• single
• skip
• skipUntil
• skipWhile
• startWith
• subscribeOn
• switch
• switchMap
• switchMapTo
• take
• takeUntil
• takeWhile
• throttle
• throttleTime
• timeInterval
• timeout
• timeoutWith
• toArray
• window
• windowCount
• windowTime
• windowToggle
• windowWhen
• withLatestFrom
• zip-static
• zip
• zipAll

[staltz]

All done. Closed.

[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.