use-debounce VS awesome-debounce-promise

Github

Debouncing is the best solution. Here is a simple lib which can help https://github.com/xnimorz/use-debounce

You should debounce your scroll-event (https://github.com/xnimorz/use-debounce) and add your state to the condition to avoid useless setState

What you're looking for is a debounce. It's not hard to implement, you can find an example here or install one from some generic hook library

use-debounce - A debounce hook for react

Tailwind Styles: https://github.com/vadimdemedes/tailwind-rn Storage: https://react-native-async-storage.github.io/async-storage/docs/api Navigation: https://reactnavigation.org/ Audio: https://docs.expo.io/versions/v41.0.0/sdk/audio/ Animations: https://github.com/oblador/react-native-animatable Modal: https://github.com/react-native-modal/react-native-modal Confetti: https://github.com/cdvntr/react-native-confetti Debounce: https://github.com/xnimorz/use-debounce Toast: https://github.com/calintamas/react-native-toast-message

useDebounce hooks - it’s name represents - used for debouncing. It is used to postpone execution to a later time like setTimeout in React Native.

I just use this for my projects: https://github.com/xnimorz/use-debounce

I have a functional component built around the React Table component that uses the Apollo GraphQL client for server-side pagination and searching. I am trying to implement debouncing for the searching so that only one query is executed against the server once the user stops typing with that value. I have tried the lodash debounce and awesome debounce promise solutions but still a query gets executed against the server for every character typed in the search field.