-
Notifications
You must be signed in to change notification settings - Fork 0
Conversation
Coverage report for
|
St.❔ |
Category | Percentage | Covered / Total |
---|---|---|---|
🟢 | Statements | 83.27% | 846/1016 |
🟡 | Branches | 68.31% | 222/325 |
🟡 | Functions | 75.46% | 163/216 |
🟢 | Lines | 82.81% | 795/960 |
Test suite run success
168 tests passing in 54 suites.
Report generated by 🧪jest coverage report action from 19cd99d
@@ -31,6 +33,10 @@ export default function SearchPagination({ | |||
}: SearchPaginationProps) { | |||
const { pending } = useFormStatus(); | |||
|
|||
const debouncedHandlePageChange = useDebouncedCallback((newPage: number) => { | |||
handlePageChange(newPage); | |||
}, DEBOUNCE_TIME); |
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.
(just curious) Does this mean there will always be a 500
delay? Even on the first click?
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.
Basically yes - I wanted to have a quick meeting also - that's why this is still in draft.
I also would need to update some of the e2e tests to wait for page change
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.
Sounds good. Let's meet to talk it thru. There might be a different UX we could use — e.g. instead of debouncing, disable the pagination while results are loading.
Fixes #2074 - Add 300ms debounce on pagination
Summary
Fixes #51
Time to review: 3 min
Changes proposed
Screen.Recording.2024-05-24.at.5.12.51.PM.mov