My strategy for this sort of thing is to only send the new request when the old (stale) request returns. That works fine without signals.
Mark > On Jul 8, 2016, at 6:19 AM, Charlie Koster <[email protected]> wrote: > > Now that signals are gone I'm not quite sure how I would debounce inputs. The > typical example is an auto-complete search box or a typeahead. > > In Elm 0.17, what is the recommended way for debouncing inputs/actions > received in the update function? If on every keypress on an input box my > update function is called and it returns a task to perform a new search based > on that input, I wouldn't want to make http requests on every keypress. I'd > want to debounce those requests. > -- > You received this message because you are subscribed to the Google Groups > "Elm Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
