supermemory/apps
addyCooks 5eeebec643 test(mcp): restore SupermemoryClient coverage and fix two blank error messages
#1406 shipped the API-error unwrapping and the status-aware handleError
fallbacks with a test file that had already been deleted in #1397, so
SupermemoryClient - every outbound API call, extractApiErrorMessage, and
all of handleError - had no coverage at all.

Restores src/server/client/index.test.ts with 53 cases covering the SDK
wiring, space scoping, result normalisation, forgetMemory's exact-match
and similarity fallbacks, the raw-fetch endpoints, and the full status
table.

Two of those cases failed against the untested code:

- A 403 whose body is {"error": ""} leaked the raw JSON envelope to the
  user, because extractApiErrorMessage falls through to the raw string
  when the recognised key holds an empty value. An envelope we parsed
  but that carries no message now yields undefined so the caller reaches
  its scope-aware fallback.
- A status outside the mapped switch (409, 413, ...) with an empty body
  reached the user as an Error with an empty message. Unmapped statuses
  with no message now report the status instead.
2026-08-26 01:40:19 +05:30
..
browser-extension fix(browser-extension): run wxt prepare before type checking (#1557) 2026-08-19 19:23:52 +05:30
docs docs: historical backfill guide (#1474) 2026-08-14 20:46:21 +00:00
mcp test(mcp): restore SupermemoryClient coverage and fix two blank error messages 2026-08-26 01:40:19 +05:30
memory-graph-playground fix: add type checks for TypeScript workspaces (#1447) 2026-08-13 17:55:50 +05:30
raycast-extension feat: mobile responsive, lint formats, toast, render issue fix (#688) 2026-01-21 03:11:53 +00:00
web fix(web): scope the ?view=mcp guest exemption to / (#1553) 2026-08-19 18:33:58 +05:30