Skip to content
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

Handling Data Races #153

Open
wgottschalk opened this issue Oct 27, 2017 · 1 comment
Open

Handling Data Races #153

wgottschalk opened this issue Oct 27, 2017 · 1 comment

Comments

@wgottschalk
Copy link

wgottschalk commented Oct 27, 2017

I want to build an autocomplete box. One of the requirements is that the user should always receive the latest input. I can throttle the inputs but that only works on a good connection. When I get to 3G network connectivity, I can end up getting multiple responses that may or may not be out of order.

What I need is a hook similar to the bailout, but it gets executed after the request has resolved, but before we dispatch the REQUEST_SUCCESS action.

@unrevised6419
Copy link
Collaborator

unrevised6419 commented Feb 13, 2018

Maybe use debounce instead of throttling. Make only one request when user stops writing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants