Open fluidsonic opened 4 years ago
@fluidsonic
If I'm not wrong.
The above throttleLatest
example should print 0
, 4
.
The operator you want seems being called throttleFirst
.
Plese see https://github.com/ReactiveX/RxJava/wiki/Filtering-Observables#throttlefirst
@jxdabc you're right, throttleFirst
is more appropriate for solving the problem. I'll update the issue.
We have no operator that prevents subsequent emissions for a certain time after an emission. In RxJava there is
throttleFirst
for that.The example above should print
0
and5
. Both should be emitted without any added delay.One use-case is button clicks where (accidental) repeated clicks should be filtered. If I click a button twice accidentally, only the first click event would make it downstream and the second click be ignored because it came in too fast after the first one.
debounce(500)
is not suitable because it a) delays the emission of the first value by at least 500ms and b) delays the emission of any value until the user stops clicking for at least 500ms.sample(500)
is not suitable because it a) delays the emission of the first value by 500ms and b) emits nothing if theFlow
is closed within 500ms after collection has started.The related
throttleLatest
was mentioned in #1107 but no reason was given why it nor it's siblings have made it intoFlow
so far.