chore(frontend): silence react-hooks/set-state-in-effect on UserList load effect

The effect intentionally reloads when the memoized load callback's identity changes (i.e. when filter dropdowns/queryValue change), which is the documented use of useCallback-as-dep. The new React 19 lint rule flags any setState inside an effect as cascading-render risk. Adding a directed disable with rationale instead of refactoring, since the current behavior is intended UX (live filter response).

chore(frontend): silence react-hooks/set-state-in-effect on UserList load effect
The effect intentionally reloads when the memoized load callback's identity changes (i.e. when filter dropdowns/queryValue change), which is the documented use of useCallback-as-dep. The new React 19 lint rule flags any setState inside an effect as cascading-render risk. Adding a directed disable with rationale instead of refactoring, since the current behavior is intended UX (live filter response).
zichun
1 parent afe6613a
Showing 1 changed file with 1 additions and 0 deletions
frontend/src/pages/usr/UserList.tsx
@@ -63,6 +63,7 @@ export default function UserList() {
     }
   }, [pageSize, queryField, matchType, queryValue])
  
+  // eslint-disable-next-line react-hooks/set-state-in-effect -- intentional reload when filter callback identity changes
   useEffect(() => { load(1) }, [load])
  
   const handleAdd = () => {