-
Notifications
You must be signed in to change notification settings - Fork 6
RTKQ Migration: Site search #1826
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
Conversation
I was toying between using debounce and throttle here, but went with a debounce with both leading and trailing set. This makes it instantly responsive on first use, but waits until the timeout has passed entirely once if there are multiple presses. Truthfully this probably doesn't *need* a debounce here since it's unlikely someone would spam enter alongside typing their query, but it doesn't hurt.
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1826 +/- ##
==========================================
+ Coverage 41.73% 42.08% +0.35%
==========================================
Files 542 542
Lines 23685 23670 -15
Branches 7855 6998 -857
==========================================
+ Hits 9884 9961 +77
+ Misses 13757 13664 -93
- Partials 44 45 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
axlewin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The search logic looks good, as does the main search page.
This breaks header search, though, where onSearch isn't defined.
Migrates the site search logic to RTKQ.