[amitbardos]

Why

The @base44/platform/react reference was hard to read. It was four pages: useChat, ChatBackend, ChatItem and ChatQuestion. Each had more types appended to it, and an unlabelled "Methods" section (send, create, clearError) appeared in the middle of useChat. The chat module, by contrast, is one page with its types as definitions under it.

What

useChat is now one page, laid out like the chat module page:

• Overview: the signature, then Parameters, Returns and Example.
• Actions: send(), create(), clearError().
• Backend calls: createApp(), openLiveSession(), sendMessage(), submitToolCallInput().
• Type Definitions: ChatItem, ChatStep, ChatAnswer, ChatStatus, ChatConnection, ChatError, ChatApp, ToolCallAnswer.
• Questions: ChatQuestion, then each kind with its methods nested under it (answer(), submit(), approve(), decline()) and its entry types.

ChatOptions has no section of its own, since Parameters already documents every option. The config for all this is appended-articles.json, page-sections.json and a new types-to-delete-after-processing.json in packages/platform.

Pipeline

Three generic pieces in the shared pipeline. The app SDK reference generates byte-identical, and so do the Platform SDK's other pages:

• nestUnderGroupTypes: in a type definition group, a type's own methods arrive at the level of the types themselves. They now nest under their type, and the bare "Methods" label goes.
• propertiesAsFields: a type's properties become fields up to its first method (name()), which keeps its heading. Before, a nested method would have been swallowed as a field.
• fixInPageAnchors: a last pass that checks every in-page link against the page's headings and explicit ids.
  • A link to a type whose section was renamed (typesWithOwnMethods) follows the new heading, for example #chatbackend → #backend-calls.
  • A link to something the page no longer has keeps its text and loses the link, so it can't jump to nothing. An example is UseChatResult.status, which is now a field.

Testing

• Unit tests for each piece in tests/unit/typedoc-mintlify.test.ts. Undoing any one of them fails a test.
• vitest run tests/unit in packages/sdk: 387 passed.
• Both references regenerated and compared page by page.
• Checked in a local Mintlify preview. The React nav has one page, and every in-page link on useChat resolves.

🤖 Generated with Claude Code

[github-actions]

🚀 Package Preview Available!

---

Install this PR's preview build with npm:

npm i @base44-preview/sdk@0.8.56-pr.346.ce5b5be

Prefer not to change any import paths? Install using npm alias so your code still imports @base44/sdk:

npm i "@base44/sdk@npm:@base44-preview/sdk@0.8.56-pr.346.ce5b5be"

Or add it to your package.json dependencies:

{
  "dependencies": {
    "@base44/sdk": "npm:@base44-preview/sdk@0.8.56-pr.346.ce5b5be"
  }
}

• 📦 Preview Package: @base44-preview/sdk@0.8.56-pr.346.ce5b5be
• 🔗 View this commit on GitHub

---

_{Preview published to npm registry — try new features instantly!}

[github-actions]

🚀 Package Preview Available! (@base44/platform)

---

Install this PR's preview build with npm:

npm i @base44-preview/platform@0.5.0-pr.346.ce5b5be

Prefer not to change any import paths? Install using npm alias so your code still imports @base44/platform:

npm i "@base44/platform@npm:@base44-preview/platform@0.5.0-pr.346.ce5b5be"

Or add it to your package.json dependencies:

{
  "dependencies": {
    "@base44/platform": "npm:@base44-preview/platform@0.5.0-pr.346.ce5b5be"
  }
}

• 📦 Preview Package: @base44-preview/platform@0.5.0-pr.346.ce5b5be
• 🔗 View this commit on GitHub

---

_{Preview published to npm registry — try new features instantly!}