You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix README examples: replace live: "catchup" with live: false
The API uses `live: false` for catch-up-only mode (get existing data, then stop).
The non-existent `live: "catchup"` value was used in examples.
Updated all code examples to use the correct `live: false` syntax.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <[email protected]>
@@ -299,11 +299,11 @@ Offsets are opaque tokens that identify positions within a stream:
299
299
-**Server-generated** - Always use the `offset` value returned in responses
300
300
301
301
```typescript
302
-
// Start from beginning (catchup mode)
303
-
const result =awaitstream.read({ offset: "-1", live: "catchup" })
302
+
// Start from beginning (catch-up mode)
303
+
const result =awaitstream.read({ offset: "-1", live: false })
304
304
305
305
// Resume from last position (always use returned offset)
306
-
const next =awaitstream.read({ offset: result.offset, live: "catchup" })
306
+
const next =awaitstream.read({ offset: result.offset, live: false })
307
307
```
308
308
309
309
The only special offset value is `"-1"` for stream start. All other offsets are opaque strings returned by the server—never construct or parse them yourself.
@@ -508,8 +508,8 @@ Build event-sourced systems with durable event logs:
0 commit comments