Overview - Ai

ai

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
docs/chat-fetcher-server-functions
6b495eb8 docs(chat): clarify fetcher vs stream is async-vs-sync, not Response-vs-iterable A `fetcher` can also return an `AsyncIterable<StreamChunk>` (sync or `Promise`-wrapped), not just a `Response` — the previous tip implied a clean Response/iterable split. The real distinction is that `stream()`'s factory must return the iterable *synchronously*, so an async server-function call (always a `Promise`) needs `fetcher` regardless of what it resolves to. Also corrects the pre-existing `stream()` section, which listed "TanStack Start server functions" as a `stream()` use case — those are async and hit the #509 type error; redirect them to `fetcher` and reframe `stream()` as the synchronous in-process / RSC / test path. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
by Tom Beckenham
Succeeded
docs/chat-fetcher-server-functions
6b495eb8 Merge ef0bcfab058b722d0bec400cfe576cf55961bbc1 into 86cf41c5ea994a7086e976f742d12cbf09cfce3e
by Tom Beckenham
Succeeded
docs/chat-fetcher-server-functions
21410cd1 docs(chat): correct fetcher/stream comparison Drop the "retries" claim (no such feature — the only `retry` in the client is SSE `retry:` control-line parsing) and fix the `stream()` factory description (it returns an `AsyncIterable<StreamChunk>`; it isn't a zero-arg factory). State the verifiable structural fact instead: `fetcher` normalizes to the same request-scoped adapter as `stream()`. Verified the server snippet typechecks without an `as any` cast. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
by Tom Beckenham
Succeeded
docs/chat-fetcher-server-functions
21410cd1 Merge 0793ab7ed9dcd60972b7f921af087b0653ecbab7 into 86cf41c5ea994a7086e976f742d12cbf09cfce3e
by Tom Beckenham
Succeeded
docs/chat-fetcher-server-functions
1d9b0d1f docs(chat): document the `fetcher` chat transport for server functions PR #512 added a first-class `fetcher` option to `useChat`/`ChatClient` for wiring a TanStack Start server function (that returns an SSE `Response`) into chat, but the connection-adapters page only covered the `stream()` path. Add a "Server Functions via `fetcher`" section, a "Pick a Transport" row, and a keyword so the new capability is discoverable. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
by Tom Beckenham
Succeeded
docs/chat-fetcher-server-functions
1d9b0d1f Merge 5a82e915919350f60c1511b5cb2298f9af6c3da7 into 86cf41c5ea994a7086e976f742d12cbf09cfce3e
by Tom Beckenham