Observable.timer unexpected/undocumented for large timeouts

RxJS version: 5.5.2

Code to reproduce:

Rx.Observable
    .timer(new Date(2017, 10, 28))
    .subscribe(() => {
        console.log('Immediate emit');
    });

Expected behavior: Should emit about a month from today (Oct 27, 2017).

Actual behavior: Emits immediately.

Additional information: I gather the timers has a max value of 2147483647 (2^31-1), and it makes sense to have such a limitation, but I would suggest an argument check and/or a warning or note in the documentation. An error seems justified as I cannot imagine someone passing in a value greater than that an expecting a 1 ms timeout.

[rohiievych]

Here is a workaround for large timeouts: timer().pipe(delay(timeout))

[benlesh]

We could test to see if it’s more than 2147483647, and if so, schedule an interval… basically something like this:

if (ms > 2147483647) {
  const MAX = 2147483647;
  const n = Math.floor(ms / MAX)
  const r = ms % MAX;
  return concat(timer(MAX, MAX).pipe(take(n)), timer(r)).pipe(takeLast());
} else {
  // usual timer path here.
}

I mean we could make it work… I’d probably do something more efficient than whats up there. A setInterval with a counter or something. Or add support directly to the AsapScheduler.

However it seems like it would be really weird for someone to want to do this, and they could just as easily do what I did above.