mirror of
https://github.com/vector-im/element-call.git
synced 2026-01-30 03:15:55 +00:00
047b3ffded
* Avoid reactivity bugs in how we track external state
Many of our hooks which attempt to bridge external state from an EventEmitter or EventTarget into React had subtle bugs which could cause them to fail to react to certain updates. The conditions necessary for triggering these bugs are explained by the tests that I've included.
In the majority of cases, I don't think we were triggering these bugs in practice. They could've become problems if we refactored our components in certain ways. The one concrete case I'm aware of in which we actually triggered such a bug was the race condition with the useRoomEncryptionSystem shared secret logic (addressed by a1110af6d5).
But, particularly with all the weird reactivity issues we're debugging this week, I think we need to eliminate the possibility that any of the bugs in these hooks are the cause of our current headaches.
* Reuse useTypedEventEmitterState in useLocalStorage
* Fix type error
26 lines
799 B
TypeScript
26 lines
799 B
TypeScript
/*
|
|
Copyright 2023-2025 New Vector Ltd.
|
|
|
|
SPDX-License-Identifier: AGPL-3.0-only OR LicenseRef-Element-Commercial
|
|
Please see LICENSE in the repository root for full details.
|
|
*/
|
|
|
|
import { useCallback, useMemo, useSyncExternalStore } from "react";
|
|
|
|
/**
|
|
* React hook that tracks whether the given media query matches.
|
|
*/
|
|
export function useMediaQuery(query: string): boolean {
|
|
const mediaQuery = useMemo(() => window.matchMedia(query), [query]);
|
|
|
|
const subscribe = useCallback(
|
|
(onChange: () => void) => {
|
|
mediaQuery.addEventListener("change", onChange);
|
|
return (): void => mediaQuery.removeEventListener("change", onChange);
|
|
},
|
|
[mediaQuery],
|
|
);
|
|
const getState = useCallback(() => mediaQuery.matches, [mediaQuery]);
|
|
return useSyncExternalStore(subscribe, getState);
|
|
}
|