Nicholas Jamieson

You could make this a little bit simpler by taking advantage of the fact that `auditTime` accepts a `Scheduler`: ```ts selectBox$.pipe( auditTime(0, animationFrameScheduler), withLatestFrom(mousemove$, ...), filter(() => this.selectOnDrag), filter(({ selectBox...

Kwinten, it's been a while since I last poked around in the `Scheduler`-related parts of the RxJS source, but I'm pretty sure that when using a scheduler, an action is...

Kwinten, I'll re-read your comment in the morning - it's late, here - but I'm not convinced that anything is scheduled in `audit` other than the `timer` that's returned by...

@d3lm I've not given it too much thought, but I don't see the harm of using the animation frame scheduler. It's the fact that you chose 16 milliseconds that suggests...

FWIW, I needed to do this with a rule of my own - that I'd deprecated in favour of a new rule that took options - and I did it...

This library was written before RxJS had an official, public testing API. Now that it does, this library is little more than a thin wrapper around `TestScheduler#run`. Any support for...

There's no way around the asynchrony that's inherent in promises. Native promises cannot be monkey patched. I would use the [`observe` helper](https://github.com/cartant/rxjs-marbles#observe) that's in this package. Also, IIRC, Ben talked...

It avoids some boilerplate. That's all.

Nope. You cannot use `hot` and `cold` without the `TestScheduler` and virtual time. Use subjects for hot observables and `of` for cold, etc.

@LogvinovLeon I put a fair bit of time into it and raised [this issue](https://github.com/palantir/tslint/issues/2876). IIRC, that situation might have been fixed, but others were still broken. I gave up on...