-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
debounce/throttle operator that always emits the last value #287
Comments
Actually I misread the documentation, but I'm still not 100% sure either |
Yeah, it does look like if the source signal terminates before the given interval, no more cached values are emitted. This is not documented, and I'm not sure if it's desired behavior. Either way, it would be nice to have an operator that doesn't behave this way. |
It was documented before the revision. Guess we should put it back, alongside an option. A |
That makes sense to me 👍 Or maybe |
@andersio Would it be welcome if I picked up this issue and created an implementation? |
@Qata Sure. 👍 |
Hello. 👋 Thanks for opening this issue. Due to inactivity, we will soft close the issue. If you feel that it should remain open, please let us know. 😄 |
I just found myself needing such an operator. I have a
SignalProducer<[Data], NoError>
created with this custom operator:I want to limit how often I get updated arrays, but I do want to make sure that the last value (which will contain all the elements), is always emitted.
The text was updated successfully, but these errors were encountered: