Rxjs: debounce/debounceTime events bug?

[rickmed]

RxJS version:
beta 4
Code to reproduce:

Input$ //observable of keyboard events
      .do( x=> console.log(x))
      .debounceTime(1000)
      .do( x=> console.log(x))

result:

Expected behavior:
The event object to be passed as it was received

Actual behavior:
All values are passed as null

Additional information:
with throttleTime it works as expected

Input$  //observable of keyboard events
      .do( x=> console.log(x))
      .throttleTime(1000)
      .do( x=> console.log(x))

EDIT: Idem with debounce.

[staltz]

Seems like a legit bug IMO. @kwonoj @blesh this is interesting, it seems those properties are lost just because the value this.lastValue is stored as a property of DebounceTimeSubscriber https://github.com/ReactiveX/rxjs/blob/master/src/operator/debounceTime.ts#L71 while in RxJS v4 the value x is passed to the scheduled dispatch through the closure: https://github.com/Reactive-Extensions/RxJS/blob/master/src/core/linq/observable/debounce.js#L45

[kwonoj]

yes, interesting. I'll look this on my end too.

[staltz]

@rickmed I assumed you used Chrome. But which version?

[rickmed]

@staltz Version 49.0.2623.110 m

[benlesh]

SyntheticKeyboardEvent <--

This is because you're using React. In React, you need to call e.persist() on events or they will mutate.

For more information see the React documentation

[lock[bot]]

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.