fix(test): type MetricsBar's useAsync mock against the real hook shape (Closes #429) - #437
Merged
Jagadeeshftw merged 1 commit intoAug 29, 2026
Annotations
9 warnings
|
Complete job
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Lint:
src/lib/types.test.ts#L20
'_' is assigned a value but never used
|
|
Lint:
src/hooks/useAsync.ts#L87
The ref value 'refreshWaiters.current' will likely have changed by the time this effect cleanup function runs. If this ref points to a node rendered by React, copy 'refreshWaiters.current' to a variable inside the effect, and use that variable in the cleanup function
|
|
Lint:
src/components/ToastProvider.test.tsx#L287
'secondToast' is assigned a value but never used
|
|
Lint:
src/components/ToastProvider.test.tsx#L286
'firstToast' is assigned a value but never used
|
|
Lint:
src/components/ToastProvider.test.tsx#L269
'toast' is assigned a value but never used
|
|
Lint:
src/components/PoolsPanel.tsx#L52
The 'pools' conditional could make the dependencies of useMemo Hook (at line 80) change on every render. To fix this, wrap the initialization of 'pools' in its own useMemo() Hook
|
|
Lint:
src/components/PoolsPanel.tsx#L52
The 'pools' conditional could make the dependencies of useMemo Hook (at line 76) change on every render. To fix this, wrap the initialization of 'pools' in its own useMemo() Hook
|
|
Lint:
src/components/PoolsPanel.tsx#L52
The 'pools' conditional could make the dependencies of useMemo Hook (at line 72) change on every render. To fix this, wrap the initialization of 'pools' in its own useMemo() Hook
|
background
wait
wait-all
cancel
parallel
Loading