Skip to content

refactor(memory-browser-panel): migrate 12 bare fetch to apiFetch#694

Open
jun261930-tech wants to merge 2 commits into
builderz-labs:mainfrom
jun261930-tech:migrate/memory-browser-panel
Open

refactor(memory-browser-panel): migrate 12 bare fetch to apiFetch#694
jun261930-tech wants to merge 2 commits into
builderz-labs:mainfrom
jun261930-tech:migrate/memory-browser-panel

Conversation

@jun261930-tech
Copy link
Copy Markdown

Summary

Migrate 12 bare fetch calls in memory-browser-panel.tsx to apiFetch.

Changes

  • Memory list / detail / search / pin / archive / delete flows now use apiFetch
  • { raw: true } preserves status branching

Validation

  • typecheck: 0 errors
  • lint: 0 errors (file-level)

P1 of MC code-quality plan (see PLAN.md / PR-api-client.md):

- src/lib/api-client.ts          (+120) ApiError + apiFetch<T> wrapper
- src/lib/__tests__/api-client.test.ts (+108) 8 vitest cases (200/401/403/500/network/loop/204/no-redirect)
- src/components/auth-expired-listener.tsx (+30) global mc:auth-expired -> /login redirect
- src/app/layout.tsx             (+2) register listener
- eslint.config.mjs              (+31) no-restricted-syntax warn for bare fetch('/api/...')

Quality gates passed:
- pnpm vitest run src/lib/__tests__/api-client.test.ts: 8/8 (2.5s)
- pnpm typecheck: 0 error
- pnpm lint: 0 error, 343 warn (~baseline 334 bare fetch + 9 pre-existing)

Out of scope: migrating existing 334 bare fetch sites (P2, separate PR).

P0 verification: playwright captured 19/19 /api/* returning 200 after login,
ruling out backend issue (cookie expired) — see p0-network-evidence.txt.
@jun261930-tech jun261930-tech requested a review from 0xNyk as a code owner May 17, 2026 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant