mirror of
https://github.com/temetro/temetro.git
synced 2026-07-26 11:58:14 +00:00
e8f3ed9ffe
`npm run lint` reported 99 errors and 26 warnings across 65 files and had presumably been failing for a while — next.config.ts sets eslint.ignoreDuringBuilds, so the build never surfaced it. 68 were in vendored code: components/charts and components/ai-elements, pulled from upstream registries. Re-linting those reports upstream's style back at us, and "fixing" them means diverging and eating conflicts on every update — ai-elements already has exactly this carve-out on the TypeScript side via ignoreBuildErrors. Ignore both, plus the two registry files in components/ui (carousel publishes its api from an effect; the sidebar skeleton picks a random width). The other 31 were ours, nearly all react-hooks/set-state-in-effect on the same shape: an effect that re-seeds form state when a dialog opens or a selection changes. Moved to render-phase adjustment, which is both what React recommends and a real fix — the effect version paints one frame of the *previous* record's values before correcting itself. Two carried sharper bugs: the employee dialog could keep a typed password across a switch to another member, and use-wallet-sync could carry `linked` over to a newly-selected patient, briefly offering to push a record to someone else's wallet. The rest: useIsMobile and speech-support detection become useSyncExternalStore (correct on first paint, no mount flash); refs mirroring state are written in effects rather than during render; the care-team fetch moves into its effect behind a reload key, dropping an exhaustive-deps suppression. Two effects in chat-panel keep the rule disabled with a reason. Both are what effects are for: draining the queued-message buffer when the transport goes idle, and resolving ?thread from the URL — the latter mints an id with nanoid(), so moving it into render would just trade this error for a purity one. Also removes a dead /explore-era import and unused directives found on the way. lint now exits 0, with the ai-elements tsc carve-out unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
53 lines
1.7 KiB
TypeScript
53 lines
1.7 KiB
TypeScript
"use client";
|
|
|
|
import { useEffect, useState } from "react";
|
|
|
|
// Returns true while the given stream's audio is above a speaking threshold —
|
|
// used to draw a Discord-style "speaking" ring around a participant's tile.
|
|
// Degrades silently if the Web Audio API isn't available.
|
|
export function useSpeaking(stream: MediaStream | null): boolean {
|
|
const [speaking, setSpeaking] = useState(false);
|
|
|
|
// Stop reporting "speaking" the moment the stream goes away or changes, so a
|
|
// muted tile can't keep a stale ring. Adjusted during render rather than in
|
|
// the effect below, which is only for driving the Web Audio graph.
|
|
const [prevStream, setPrevStream] = useState(stream);
|
|
if (prevStream !== stream) {
|
|
setPrevStream(stream);
|
|
setSpeaking(false);
|
|
}
|
|
|
|
useEffect(() => {
|
|
if (!stream || stream.getAudioTracks().length === 0) return;
|
|
let ctx: AudioContext | null = null;
|
|
let raf = 0;
|
|
try {
|
|
ctx = new AudioContext();
|
|
const source = ctx.createMediaStreamSource(stream);
|
|
const analyser = ctx.createAnalyser();
|
|
analyser.fftSize = 512;
|
|
source.connect(analyser);
|
|
const data = new Uint8Array(analyser.frequencyBinCount);
|
|
const tick = () => {
|
|
analyser.getByteTimeDomainData(data);
|
|
let sum = 0;
|
|
for (let i = 0; i < data.length; i++) {
|
|
const v = (data[i]! - 128) / 128;
|
|
sum += v * v;
|
|
}
|
|
setSpeaking(Math.sqrt(sum / data.length) > 0.045);
|
|
raf = requestAnimationFrame(tick);
|
|
};
|
|
tick();
|
|
} catch {
|
|
/* no Web Audio — no ring */
|
|
}
|
|
return () => {
|
|
cancelAnimationFrame(raf);
|
|
ctx?.close().catch(() => {});
|
|
};
|
|
}, [stream]);
|
|
|
|
return speaking;
|
|
}
|