Description
We have no operator that prevents subsequent emissions for a certain time after an emission.
In RxJava there is throttleFirst
for that.
flow {
repeat(10) {
emit(it)
delay(101)
}
}
.throttleFirst(500)
.collect {
println(it)
}
The example above should print 0
and 5
. 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 the Flow
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 into Flow
so far.