第一次渲染组件时,useCallback
钩子会将传递的函数作为其参数并将其存储在幕后。当您调用回调时,它会调用您的函数。到现在为止还挺好。
第二次渲染组件时,useCallback
钩子会检查你传入的依赖项。如果它们没有改变,你传入的函数将被完全忽略!当您调用回调时,它将调用您在第一次渲染时传入的函数,该函数仍引用该时间点的相同值。这与您作为依赖项传入的值无关 - 它只是普通的 JavaScript 闭包!
当依赖关系发生变化时,useCallback
钩子会接受你传入的函数并替换它存储的函数。当您调用回调时,它将调用新版本的函数。
所以换句话说,没有“冻结”/有条件更新的变量——它只是存储一个函数然后重新使用它,没有比这更花哨的了:)
编辑:这是一个演示纯 JavaScript 中发生的事情的示例:
// React has some component-local storage that it tracks behind the scenes.
// useState and useCallback both hook into this.
//
// Imagine there's a 'storage' variable for every instance of your
// component.
const storage = {};
function useState(init) {
if (storage.data === undefined) {
storage.data = init;
}
return [storage.data, (value) => storage.data = value];
}
function useCallback(fn) {
// The real version would check dependencies here, but since our callback
// should only update on the first render, this will suffice.
if (storage.callback === undefined) {
storage.callback = fn;
}
return storage.callback;
}
function MyComponent() {
const [data, setData] = useState(0);
const callback = useCallback(() => data);
// Rather than outputting DOM, we'll just log.
console.log("data:", data);
console.log("callback:", callback());
return {
increase: () => setData(data + 1)
}
}
let instance = MyComponent(); // Let's 'render' our component...
instance.increase(); // This would trigger a re-render, so we call our component again...
instance = MyComponent();
instance.increase(); // and again...
instance = MyComponent();