mirror of
https://github.com/supermemoryai/supermemory.git
synced 2026-10-27 06:15:15 +00:00
f3001517d1
## Why The document operations guide did not describe how to retrieve extracted text from a v5 document list, and the migration guide incorrectly said the list `include` object was for memories only. ## What changed - Document `include.content`, its `false` default, and a cURL request for uploaded files in the same section pattern as the surrounding guide. - Explain that list content is the last published extracted text, including the behavior before first publication and during failed replacement. - Correct the v5 migration and reference overview copy. ```mermaid flowchart LR A[Document operations guide] --> B[include.content request] B --> C[Published extracted text in list response] ``` ## Validation - Compared the guide and migration snippet with adjacent v5 docs for format and terminology. - `git diff --check` — passed. - `python3 -m json.tool apps/docs/docs.json` — passed. Related API PR: https://github.com/supermemoryai/mono/pull/3606 The written docs should publish with or after the API change. The generated v5 reference reads the deployed OpenAPI source, so it updates when that source is available and the docs site refreshes. |
||
|---|---|---|
| .. | ||
| agent-prompt-panel.jsx | ||
| agent-prompt.jsx | ||
| api-v5-agent-prompt.mdx | ||
| api-v5-completion.mdx | ||
| api-v5-content-management.mdx | ||
| api-v5-document-ingestion.mdx | ||
| api-v5-document-updates.mdx | ||
| api-v5-filters.mdx | ||
| api-v5-memory-forgetting.mdx | ||
| api-v5-namespaces.mdx | ||
| api-v5-organization.mdx | ||
| api-v5-overview.mdx | ||
| api-v5-profiles.mdx | ||
| api-v5-rollout.mdx | ||
| api-v5-sdks.mdx | ||
| api-v5-search.mdx | ||
| getting-api-key.mdx | ||
| hero-samples.jsx | ||
| journey.mdx | ||
| migrate-cli.mdx | ||
| slack-message.mdx | ||