-
Notifications
You must be signed in to change notification settings - Fork 63
Conversation
Hi, @zackkrida i see that it also happened here #2090 |
@obulat would probably know best how to debug this issue quickly 🤞 |
@anton202, I think you opened this PR before the If there are still problems with the e2e remaining, I think we will also need to change the I tried rebasing your branch onto main, and changing the functions to what's listed below, and didn't get any errors in e2e tests locally.
|
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.
Thank you for your fix, @anton202, it works perfectly! I've added notes about the tests, and I'll approve after they are fixed.
@obulat Thank you for the help. i`ll adress that on sunday :) |
@obulat i`ve tried your suggestion but the test still didnt pass :( |
@anton202 Sorry for the delay in responses on this PR, folks have been travelling the past week and doing work offline. Most will be back later in the week and someone will be able to help debug more closely. We appreciate the patience 🙏 |
sure, no problem :) |
Co-authored-by: Zack Krida <zackkrida@pm.me>
Co-authored-by: Zack Krida <zackkrida@pm.me>
Based on the medium urgency of this PR, the following reviewers are being gently reminded to review this PR: @dhruvkb Excluding weekend1 days, this PR was updated 4 day(s) ago. PRs labelled with medium urgency are expected to be reviewed within 4 weekday(s)2. @anton202, if this PR is not ready for a review, please draft it to prevent reviewers from getting further unnecessary pings. Footnotes |
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.
LGTM and it works. But I have a question about the wait numbers. A code comment //
explaining them would be good.
() => searchStore.searchQueryParams, | ||
(newQuery: ApiQueryParams, oldQuery: ApiQueryParams) => { | ||
if (!areQueriesEqual(newQuery, oldQuery)) { | ||
router.push(searchStore.getSearchPath()) | ||
} | ||
} | ||
}, | ||
{ debounce: 800, maxWait: 5000 } |
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.
What is the reasoning behind these values?
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.
Ah I see @zackkrida wanted to raise it from 500. 800 seemed a very specific, very arbitrary choice to start with.
Fixes
Fixes #505 by @sarayourfriend
Description
as described in the issue by @sarayourfriend, currently when selecting several filters one after the other
a query will be excuted for each filter selection.
so, as suggested in the issue i added a debounce of 500ms to filter selection (basically switched the watch function to watchDebounced )
Staging
staging-filter.mp4
This PR
staging-filter.mp4
Testing Instructions
follow the steps in the video :)
Checklist
Update index.md
).main
) ora parent feature branch.
errors.
Developer Certificate of Origin
Developer Certificate of Origin