fix(links): the donate buttons funded another organisation, and two nav entries went nowhere #1796
catomeanci.yml
on: pull_request
Code Quality Checks
6m 16s
Auth Smoke Test
1m 49s
Dual-Persona Inventory Smoke
3m 17s
Migration Drift Check
34s
Local E2E Journeys
6m 59s
Run Tests
1m 35s
Dependency Security Audit
39s
Main Red Alert (dispatched)
0s
Annotations
4 warnings
|
Code Quality Checks:
src/components/timecards/useTimecardDraft.ts#L237
The 'currentSavePayload' object makes the dependencies of useCallback Hook (at line 914) change on every render. To fix this, wrap the initialization of 'currentSavePayload' in its own useMemo() Hook
|
|
Code Quality Checks:
src/components/timecards/useTimecardDraft.ts#L237
The 'currentSavePayload' object makes the dependencies of useCallback Hook (at line 799) change on every render. To fix this, wrap the initialization of 'currentSavePayload' in its own useMemo() Hook
|
|
Code Quality Checks:
src/components/auth/LoginForm.tsx#L83
Do not use `window.location.assign()` to navigate to internal Next.js pages. Use `redirect()` in the render phase, or `useRouter().push()` in Client Components' event handlers instead. See: https://nextjs.org/docs/messages/no-location-assign-relative-destination
|
|
Code Quality Checks:
src/app/admin/decisions/[id]/DecisionHeaderCard.tsx#L82
Do not use `window.location.href` to navigate to internal Next.js pages. Use `redirect()` in the render phase, or `useRouter().push()` in Client Components' event handlers instead. See: https://nextjs.org/docs/messages/no-location-assign-relative-destination
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
e2e-local-artifacts
|
1.1 MB |
sha256:f342bf6d9925f6edba086451ca3de525465c288328f387a8f9a01319ec6ceab7
|
|