The main difference between switchMap and other flattening operators is the cancelling effect. On each emission the previous inner observable (the result of the function you supplied) is cancelled and the new observable is subscribed. You can remember this by the phrase switch to a new observable.
switchMap 和其他扁平化操作符的主要区别在于取消效果。 在每次发射时，先前的内部 observable（您提供的函数的结果）被取消并订阅新的 observable。 您可以通过短语 switch to a new observable 记住这一点。
This works perfectly for scenarios like typeaheads where you are no longer concerned with the response of the previous request when a new input arrives. This also is a safe option in situations where a long lived inner observable could cause memory leaks, for instance if you used mergeMap with an interval and forgot to properly dispose of inner subscriptions. Remember, switchMap maintains only one inner subscription at a time, this can be seen clearly in the first example.
这对于像预先输入这样的场景非常有效，当新输入到达时，您不再关心先前请求的响应。 在长期存在的内部 observable 可能导致内存泄漏的情况下，这也是一个安全的选择。
Be careful though, you probably want to avoid switchMap in scenarios where every request needs to complete, think writes to a database. switchMap could cancel a request if the source emits quickly enough. In these scenarios mergeMap is the correct option.
但是要小心，您可能希望在每个请求都需要完成的情况下避免使用 switchMap，比如写入数据库的场景。 如果源发出足够快，switchMap 可以取消请求。 在这些情况下，mergeMap 是正确的选项。
看这个例子：
import { interval, fromEvent } from 'rxjs'; import { switchMap } from 'rxjs/operators'; fromEvent(document, 'click') .pipe( // restart counter on every click switchMap(() => interval(1000)) ) .subscribe(console.log);
每次点击屏幕之后，fromEvent issue 出来的 MouseEvent，传入 switchMap 内部，都会重启一个新的时间间隔为1秒的计时器，并且取消之前的定时器。打印如下：
