The best way to control Claude Code, Codex and more from any computer or phone
| 1 | import { useGT } from "gt-react"; |
| 2 | import { useEffect, useState } from "react"; |
| 3 | |
| 4 | import { useStableCallback } from "~/hooks/useStableCallback"; |
| 5 | import { observeIntersection } from "~/lib/observeIntersection"; |
| 6 | import { DiffFileHeaderSkeleton } from "../DiffPanelShell"; |
| 7 | |
| 8 | export function DiffFileLoadingBoundary({ load, count }: { load: () => void; count: number }) { |
| 9 | const gt = useGT(); |
| 10 | const [isNear, setIsNear] = useState(false); |
| 11 | const loadLatest = useStableCallback(load); |
| 12 | // A fresh observe redelivers the current intersection, so this ref must keep its identity |
| 13 | // across renders: it captures nothing but the state setter. |
| 14 | const observe = (node: HTMLDivElement | null) => { |
| 15 | if (!node) return; |
| 16 | return observeIntersection(node, (entry) => setIsNear(entry.isIntersecting), { |
| 17 | rootMargin: "600px", |
| 18 | }); |
| 19 | }; |
| 20 | // A settled batch shrinks `count` without moving the boundary out of range, and no new |
| 21 | // intersection entry arrives for that, so ask for the next batch whenever it changes. |
| 22 | // oxlint-disable-next-line t3code/no-unreasoned-state-sync -- requests the next diff batch while the boundary is near the viewport and files remain |
| 23 | useEffect(() => { |
| 24 | if (isNear && count > 0) loadLatest(); |
| 25 | }, [isNear, count, loadLatest]); |
| 26 | |
| 27 | return ( |
| 28 | <div ref={observe} role="status" aria-label={gt("Loading diff…")}> |
| 29 | {Array.from({ length: Math.min(count, 4) }, (_, index) => ( |
| 30 | <div key={index} aria-hidden className="border-b border-border/40"> |
| 31 | <DiffFileHeaderSkeleton titleWidth="medium" /> |
| 32 | </div> |
| 33 | ))} |
| 34 | </div> |
| 35 | ); |
| 36 | } |