docs: add link reference for cursed React techniques

Parkreiner · Parkreiner · commit 6ad1cf203f58 · 2025-02-07T22:54:38.000Z
diff --git a/site/src/components/Spinner/Spinner.tsx b/site/src/components/Spinner/Spinner.tsx
@@ -145,16 +145,19 @@ function useShowSpinner(loading: boolean, spinnerDelayMs: number): boolean {
 		safeDelay = 0;
 	}
 
-	// Doing a bunch of mid-render state syncs to minimize risks of UI tearing
-	// during re-renders. It's ugly, but it's what the React team officially
-	// recommends (even though this specific case is extra nasty).
-	//
-	// Be very careful with this logic; React only bails out of redundant state
-	// updates if they happen outside of a render. Inside a render, if you keep
-	// calling a state dispatch, you will get an infinite render loop, no matter
-	// what value you dispatch. There must be a "base case" in the render path
-	// that causes state dispatches to stop entirely so that React can move on
-	// to the next component in the Fiber subtree
+	/**
+	 * Doing a bunch of mid-render state syncs to minimize risks of UI tearing
+	 * during re-renders. It's ugly, but it's what the React team officially
+	 * recommends (even though this specific case is extra nasty).
+	 * @see {@link https://react.dev/learn/you-might-not-need-an-effect#adjusting-some-state-when-a-prop-changes}
+	 *
+	 * Be very careful with this logic; React only bails out of redundant state
+	 * updates if they happen outside of a render. Inside a render, if you keep
+	 * calling a state dispatch, you will get an infinite render loop, no matter
+	 * what value you dispatch. There must be a "base case" in the render path
+	 * that causes state dispatches to stop entirely so that React can move on
+	 * to the next component in the Fiber subtree
+	 */
 	const [delayLapsed, setDelayLapsed] = useState(safeDelay === 0);
 	const [renderCache, setRenderCache] = useState({ loading, safeDelay });
 	const canResetLapseOnRerender =
