docs(arch): finalize hybrid stream signature in incubation-js.md#79
Conversation
Updated `incubation-js.md` to reflect the decision to prioritize internal pipeline efficiency over developer API uniformity. - Updated Section 1.1 implementation blueprint to use `async function*` for `resolvedStream` and `mapStream`, matching the expected `AsyncIterable` outputs, while leaving `bodyStream` as `ReadableStream`. - Updated Section 2.3 to explicitly state that the hybrid signature is the final API, removing the example code that wrapped outputs using `ReadableStream.from()`. Co-authored-by: TarasMazepa <6552358+TarasMazepa@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
Updated the JavaScript SDK architectural document (
incubation-js.md) to explicitly confirm that the internal hybrid stream signature (mixingAsyncIterableandReadableStream) will act as the public API. It clarifies that maximum CPU throughput for internal parsers takes precedence over strict Web Stream uniformity for developers.PR created automatically by Jules for task 9818691536907114724 started by @TarasMazepa