Problem
react-hooks/set-state-in-effect also fires in the row/visualization UI components (separate area from #183's provider cluster):
components/pageblocks/ProblemRowReact.js:154components/pageblocks/VerifyRowReact.js:46, 52components/pageblocks/VisualizeRowReact.js:135, 139components/Visualization/QuantumCircuitVis.js:152
6 occurrences across 4 files.
Fix
Same pattern as #183 (setState called synchronously inside a useEffect) but a different code area with a different owner/review surface, so tracked separately. Restructure each effect: derive state during render, or move the update into the triggering event handler.
Acceptance
npx eslint . no longer reports react-hooks/set-state-in-effect for these 4 files, and the affected rows/visualizations still render and update correctly (manually verify in browser).
Problem
react-hooks/set-state-in-effectalso fires in the row/visualization UI components (separate area from #183's provider cluster):components/pageblocks/ProblemRowReact.js:154components/pageblocks/VerifyRowReact.js:46, 52components/pageblocks/VisualizeRowReact.js:135, 139components/Visualization/QuantumCircuitVis.js:1526 occurrences across 4 files.
Fix
Same pattern as #183 (setState called synchronously inside a
useEffect) but a different code area with a different owner/review surface, so tracked separately. Restructure each effect: derive state during render, or move the update into the triggering event handler.Acceptance
npx eslint .no longer reportsreact-hooks/set-state-in-effectfor these 4 files, and the affected rows/visualizations still render and update correctly (manually verify in browser).