fix search input desync with debounced query#2097
Merged
Conversation
ahmedshayea
reviewed
Jan 8, 2026
ahmedshayea
left a comment
ahmedshayea
left a comment
There was a problem hiding this comment.
That resolved the issue entirely.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📝 Why & how
Hopefully fixes #2096
Looks like when clearing a search input and retyping new value quickly within the debounce window (200ms) it might sometimes lead to query param and input value desync, due to
searchinduceduseEffecttriggering before debounce ended.The
useEffectblock has been added few months ago due to desync caused by pressing homepage logo link, but after changes to link element within Tailwind refactor this should no longer be a case, which made this update effect redundant.✅ Checklist
Preview
https://react-native-directory-q94s4znsj-rndir.vercel.app/