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
The content-type handler interface table documented a
`deserializeStream(stream)` property that Harper does not implement. The
`ContentTypeHandler` interface in the core repo declares only `serialize`,
`serializeStream`, `deserialize`, and `q`.
Removes the `deserializeStream` row and drops the now-dangling "Used when
`deserializeStream` is absent." clause from the `deserialize(buffer)`
description.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
| `serialize(data)` | `(any) => Buffer \|Uint8Array \| string` | Serialize data for a response |
440
-
| `serializeStream(data)` | `(any) => ReadableStream` | Serialize as a stream (for async iterables or large data) |
441
-
| `deserialize(buffer)` | `(Buffer \|string) => any` | Deserialize an incoming request body. Used when `deserializeStream` is absent. String for `text/*` types, Buffer for binary types. |
0 commit comments