-
Notifications
You must be signed in to change notification settings - Fork 949
fix(site): speed up state syncs and validate input for debounce hook logic #18877
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
Changes from all commits
9f35d9b
01850ca
264069e
9cd1c57
af376a2
9ca576b
11217cb
4266b85
b9b5c9f
c25cc8f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,18 +2,15 @@ | |
* @file Defines hooks for created debounced versions of functions and arbitrary | ||
* values. | ||
* | ||
* It is not safe to call a general-purpose debounce utility inside a React | ||
* render. It will work on the initial render, but the memory reference for the | ||
* value will change on re-renders. Most debounce functions create a "stateful" | ||
* version of a function by leveraging closure; but by calling it repeatedly, | ||
* you create multiple "pockets" of state, rather than a centralized one. | ||
* | ||
* Debounce utilities can make sense if they can be called directly outside the | ||
* component or in a useEffect call, though. | ||
* It is not safe to call most general-purpose debounce utility functions inside | ||
* a React render. This is because the state for handling the debounce logic | ||
* lives in the utility instead of React. If you call a general-purpose debounce | ||
* function inline, that will create a new stateful function on every render, | ||
* which has a lot of risks around conflicting/contradictory state. | ||
*/ | ||
import { useCallback, useEffect, useRef, useState } from "react"; | ||
|
||
type useDebouncedFunctionReturn<Args extends unknown[]> = Readonly<{ | ||
type UseDebouncedFunctionReturn<Args extends unknown[]> = Readonly<{ | ||
debounced: (...args: Args) => void; | ||
|
||
// Mainly here to make interfacing with useEffect cleanup functions easier | ||
|
@@ -34,26 +31,32 @@ type useDebouncedFunctionReturn<Args extends unknown[]> = Readonly<{ | |
*/ | ||
export function useDebouncedFunction< | ||
// Parameterizing on the args instead of the whole callback function type to | ||
// avoid type contra-variance issues | ||
// avoid type contravariance issues | ||
Args extends unknown[] = unknown[], | ||
>( | ||
callback: (...args: Args) => void | Promise<void>, | ||
debounceTimeMs: number, | ||
): useDebouncedFunctionReturn<Args> { | ||
const timeoutIdRef = useRef<number | null>(null); | ||
debounceTimeoutMs: number, | ||
): UseDebouncedFunctionReturn<Args> { | ||
if (!Number.isInteger(debounceTimeoutMs) || debounceTimeoutMs < 0) { | ||
throw new Error( | ||
`Invalid value ${debounceTimeoutMs} for debounceTimeoutMs. Value must be an integer greater than or equal to zero.`, | ||
); | ||
} | ||
|
||
const timeoutIdRef = useRef<number | undefined>(undefined); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Updated ref type to match the type used by the browser's |
||
const cancelDebounce = useCallback(() => { | ||
if (timeoutIdRef.current !== null) { | ||
if (timeoutIdRef.current !== undefined) { | ||
window.clearTimeout(timeoutIdRef.current); | ||
} | ||
|
||
timeoutIdRef.current = null; | ||
timeoutIdRef.current = undefined; | ||
}, []); | ||
|
||
const debounceTimeRef = useRef(debounceTimeMs); | ||
const debounceTimeRef = useRef(debounceTimeoutMs); | ||
useEffect(() => { | ||
cancelDebounce(); | ||
debounceTimeRef.current = debounceTimeMs; | ||
}, [cancelDebounce, debounceTimeMs]); | ||
debounceTimeRef.current = debounceTimeoutMs; | ||
}, [cancelDebounce, debounceTimeoutMs]); | ||
|
||
const callbackRef = useRef(callback); | ||
useEffect(() => { | ||
|
@@ -81,19 +84,32 @@ export function useDebouncedFunction< | |
/** | ||
* Takes any value, and returns out a debounced version of it. | ||
*/ | ||
export function useDebouncedValue<T = unknown>( | ||
value: T, | ||
debounceTimeMs: number, | ||
): T { | ||
export function useDebouncedValue<T>(value: T, debounceTimeoutMs: number): T { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Removed the default parameter here because if you, the user of the hook, don't know the type of a value you're trying to debounce, you're probably doing something really wrong |
||
if (!Number.isInteger(debounceTimeoutMs) || debounceTimeoutMs < 0) { | ||
throw new Error( | ||
`Invalid value ${debounceTimeoutMs} for debounceTimeoutMs. Value must be an integer greater than or equal to zero.`, | ||
); | ||
} | ||
|
||
const [debouncedValue, setDebouncedValue] = useState(value); | ||
|
||
// If the debounce timeout is ever zero, synchronously flush any state syncs. | ||
// Doing this mid-render instead of in useEffect means that we drastically cut | ||
// down on needless re-renders, and we also avoid going through the event loop | ||
// to do a state sync that is *intended* to happen immediately | ||
if (value !== debouncedValue && debounceTimeoutMs === 0) { | ||
setDebouncedValue(value); | ||
} | ||
useEffect(() => { | ||
if (debounceTimeoutMs === 0) { | ||
return; | ||
} | ||
|
||
const timeoutId = window.setTimeout(() => { | ||
setDebouncedValue(value); | ||
}, debounceTimeMs); | ||
|
||
}, debounceTimeoutMs); | ||
return () => window.clearTimeout(timeoutId); | ||
}, [value, debounceTimeMs]); | ||
}, [value, debounceTimeoutMs]); | ||
|
||
return debouncedValue; | ||
} |
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.
Default type parameter removed to match new type signature for the main hook