fix(base): stabilize properties identity to break render loop

This commit is contained in:
Philipinho
2026-04-18 18:48:41 +01:00
parent 5a4d10081d
commit 5c11e59128
@@ -185,7 +185,11 @@ export function useBaseTable(
const updateViewMutation = useUpdateViewMutation();
const persistTimerRef = useRef<ReturnType<typeof setTimeout> | null>(null);
const properties = base?.properties ?? [];
// `base?.properties ?? []` minted a fresh `[]` every render while the
// base query was loading, which invalidated every downstream memo and
// tripped the setState-in-useEffect pairs below → "Maximum update
// depth exceeded". Memoize so the identity is stable.
const properties = useMemo(() => base?.properties ?? [], [base?.properties]);
const viewConfig = activeView?.config;
const columns = useMemo(