fix: batch and debounce rapid user input events (typing, scrolling)#415
Merged
Conversation
|
@binayyub4211 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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
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.
PR Title
fix: batch and debounce rapid user input events (typing, scrolling)
PR Description
What was done:
useDebounceanduseDebounceCallbackReact Hooks.useDebouncewith300msdelay to the search input text insideMobileSearchcomponent. Keeps the input controlled state highly responsive but debounces suggestions list calculations and results filtering automatically as the user types.useDebounceCallbackwith100msdelay toonScrollhandlers insideLessonCarouselcomponent. Safely extracts raw content offsets synchronously to bypass React Native event pooling while preventing render spams during rapid horizontal scrolling.Why it was done:
How it was verified:
tests/hooks/useDebounce.test.tsto test hook timing behavior.tests/components/DebounceIntegration.test.tsxto verify components under rapid event simulation.Closes #256