fix(docs): correct stale @supermemory/memory-graph API references

[thegoodengineer]

Summary

apps/docs/integrations/memory-graph.mdx (and, independently, apps/memory-graph-playground/README.md) document an older version of the @supermemory/memory-graph public API. Following the Quick Start, Props Reference, or Exports section as written today produces code that either fails to type-check or silently drops props the component doesn't recognize.

What's wrong (verified against packages/memory-graph/src)

• Exports section listed Legend, NodeDetailPanel, SpacesDropdown, useGraphInteractions, colors, LAYOUT_CONSTANTS. None of these are exported from packages/memory-graph/src/index.tsx. The real exports are MemoryGraph, GraphCanvas, useGraphData, useGraphTheme, four engine classes, and DEFAULT_COLORS / GRAPH_SETTINGS / etc.
• Every prop example used loadMoreDocuments, totalLoaded, selectedSpace, onSpaceChange, showSpacesSelector. None of these exist on MemoryGraphProps (packages/memory-graph/src/types.ts). The real props are onLoadMore / totalCount; the space-selector props don't exist on the component at all anymore.
• documents was typed as DocumentWithMemories[] with a fabricated shape (status, metadata, customId, ...), but MemoryGraphProps.documents is actually GraphApiDocument[] (documentType / memories), a different, incompatible shape. Code copied straight from the docs doesn't compile.
• The identical drift exists independently in apps/memory-graph-playground/README.md, confirming this isn't a one-off typo but the package's real API having moved on without the docs.

What changed

• Rewrote Exports to match packages/memory-graph/src/index.tsx exactly, and documented the previously-undocumented ./mock-data subpath export (generateMockGraphData, already used internally by the playground app).
• Rewrote Quick Start / Backend API Route / the pagination example to use GraphApiDocument[], onLoadMore, totalCount, and added a toGraphDocument mapping function, grounded in apps/web/components/memory-graph/hooks/use-graph-api.ts (the actual production code that calls /v3/documents/documents), showing how to normalize the API's type / memoryEntries fields into the documentType / memories shape the component needs.
• Removed the Controlled Space Selection example. selectedSpace / onSpaceChange / showSpacesSelector aren't props on the component anymore.
• Rewrote Props Reference to match MemoryGraphProps field-for-field, including several real props that weren't documented before (containerTags, documentIds, maxNodes, showFps, labels, layering, slideshow props, onOpenDocument).
• Rewrote Data Types to show the real GraphApiDocument / GraphApiMemory (what documents actually takes) alongside the real DocumentWithMemories / MemoryEntry (the backward-compat exports), instead of a fabricated shape.
• Fixed Variants: removed the "space selector visible/hidden" claim (no such component exists in the package); kept the 0.8x/0.5x zoom figures, which checked out against constants.ts.
• Made the Pages Router and Express tabs in Backend API Route fully self-contained (each defines its own toGraphDocument mapping) instead of referencing the App Router tab's helper, since CodeGroup tabs are alternatives a reader copies individually.
• Applied the identical corrections to apps/memory-graph-playground/README.md.

Not changed

Installation, Performance, and Browser Support sections, and the Variants zoom figures (0.8x / 0.5x). I found no evidence these are inaccurate, so I left them alone to keep the diff scoped to verified errors.

Addressed automated review feedback

Graphite's review left two comments; both are fixed:

• toGraphDocument (and the Express equivalent) never set GraphApiMemory.content, even though it's a valid field on the type. Added content: mem.content ?? null in all three mapping functions. Worth noting for context: I checked, and this field is provably unused for rendering (packages/memory-graph/src/hooks/use-graph-data.ts always overwrites it with mem.memory before a memory node is drawn), so this wasn't causing the visible "data loss" the comment described, just an unpopulated optional field. Fixed anyway since it's free and makes the mapping match the type exactly.
• The (data.documents as RawDocument[]) cast was flagged against a custom "avoid type assertions" style rule. Rather than apply the bot's literal suggested diff (which just deletes the cast and leaves data as any, i.e. less type-safe than before), I implemented what its own description asked for: a RawDocumentsResponse interface and a type annotation on data, so data.documents is RawDocument[] without any cast, in both the App Router and Pages Router tabs.

Verification

• Cross-checked every prop, type, and export against packages/memory-graph/src/{index.tsx,types.ts,api-types.ts,mock-data.ts} and packages/memory-graph/package.json's exports map.
• Cross-checked the API normalization logic against two independent real call sites: apps/web/components/memory-graph/hooks/use-graph-api.ts and apps/memory-graph-playground/src/app/page.tsx. Both convert the same type / memoryEntries to documentType / memories shape, giving two independent confirmations of the real wire format rather than a guess.
• Checked the Console/Consumer zoom claim in the Variants section against packages/memory-graph/src/constants.ts (0.8x / 0.5x initial zoom, confirmed accurate) and removed the section's "space selector visible/hidden" claim, which isn't: there's no space-selector component anywhere in packages/memory-graph/src (only six components total, none of them a dropdown/selector).
• Made every CodeGroup tab in the Backend API Route section standalone (each defines its own toGraphDocument mapping) instead of one tab silently depending on code shown only in another tab.
• biome.json has no Markdown/MDX support configured in this repo, so bun run format-lint doesn't apply to either changed file (confirmed: bunx biome check explicitly reports both as ignored, 0 files processed). Checked fence and MDX-component balance by hand instead: 34 code-fence lines (17 balanced pairs), and <CodeGroup>/<Note>/<Warning>/<Card> each open/close 1:1.
• Docs-only change, no .ts/.tsx files touched. apps/docs has no check-types or build script (see apps/docs/package.json), so this change is a structural no-op for those turbo tasks.

[graphite-app]

The toGraphDocument function drops the content field from RawMemoryEntry when mapping to GraphApiMemory. According to the GraphApiMemory interface defined at lines 389-408, content?: string | null; is a valid optional field, but it's never set in the mapping.

This causes data loss when mem.content exists and is different from mem.memory. The fix is to add the content field to the mapped object:

memories: doc.memoryEntries.map((mem): GraphApiMemory => ({
  id: mem.id,
  memory: mem.memory ?? mem.content ?? '',
  content: mem.content ?? null,  // Add this line
  isStatic: mem.isStatic ?? false,
  // ... rest of fields
}))

Without this, any distinct content in the raw API response will be silently dropped when consumed by components expecting GraphApiDocument[].

Suggested change

	memories: doc.memoryEntries.map((mem): GraphApiMemory => ({
	id: mem.id,
	memory: mem.memory ?? mem.content ?? '',
	isStatic: mem.isStatic ?? false,
	spaceId: mem.spaceId ?? '',
	isLatest: mem.isLatest ?? true,
	isForgotten: mem.isForgotten ?? false,
	forgetAfter: mem.forgetAfter ?? null,
	forgetReason: mem.forgetReason ?? null,
	version: mem.version ?? 1,
	parentMemoryId: mem.parentMemoryId ?? null,
	rootMemoryId: mem.rootMemoryId ?? null,
	createdAt: mem.createdAt,
	updatedAt: mem.updatedAt,
	relation: mem.relation ?? null,
	updatesMemoryId: mem.updatesMemoryId ?? null,
	nextVersionId: mem.nextVersionId ?? null,
	memoryRelations: mem.memoryRelations ?? null,
	spaceContainerTag: mem.spaceContainerTag ?? null,
	})),
	memories: doc.memoryEntries.map((mem): GraphApiMemory => ({
	id: mem.id,
	memory: mem.memory ?? mem.content ?? '',
	content: mem.content ?? null,
	isStatic: mem.isStatic ?? false,
	spaceId: mem.spaceId ?? '',
	isLatest: mem.isLatest ?? true,
	isForgotten: mem.isForgotten ?? false,
	forgetAfter: mem.forgetAfter ?? null,
	forgetReason: mem.forgetReason ?? null,
	version: mem.version ?? 1,
	parentMemoryId: mem.parentMemoryId ?? null,
	rootMemoryId: mem.rootMemoryId ?? null,
	createdAt: mem.createdAt,
	updatedAt: mem.updatedAt,
	relation: mem.relation ?? null,
	updatesMemoryId: mem.updatesMemoryId ?? null,
	nextVersionId: mem.nextVersionId ?? null,
	memoryRelations: mem.memoryRelations ?? null,
	spaceContainerTag: mem.spaceContainerTag ?? null,
	})),

Spotted by Graphite



Is this helpful? React 👍 or 👎 to let us know.

[graphite-app]

The code uses a type assertion (as RawDocument[]) on data.documents instead of a type annotation. According to the style guide rule 'Use type annotations instead of assertions for object literals' and 'Avoid unnecessary type assertions', you should avoid as casts where possible. Instead, type data properly (e.g., const data: { documents: RawDocument[]; pagination: unknown } = await response.json();) so that data.documents is already typed as RawDocument[] without needing a cast.

Suggested change

	documents: (data.documents as RawDocument[]).map(toGraphDocument),
	pagination: data.pagination,
	documents: data.documents.map(toGraphDocument),
	pagination: data.pagination,

Spotted by Graphite (based on custom rule: TypeScript style guide (Google))



Is this helpful? React 👍 or 👎 to let us know.