feat(typespec-ts): streaming by l0lawrence · Pull Request #5196 · Azure/typespec-azure

Libba Lawrence (l0lawrence) · 2026-08-10T20:45:06Z

Adds structured JSONL + SSE streaming code generation to the @azure-tools/typespec-ts modular emitter. A response whose TCGC metadata indicates a structured stream now generates a Promise<AsyncIterable<T>> of deserialized items/events instead of returning the raw binary Uint8Array body. Does not contain reconnection support - depends on createStreamSSE(). Azure Search, the library requesting this feature, does not support reconnection at this point in time.

The sse spec this is based on: https://html.spec.whatwg.org/multipage/server-sent-events.html

What is generated

JSONL (JsonlStream<T>) -> Promise<AsyncIterable<T>> that lazily decodes JSON Lines.
SSE (SSEStream<T>) -> Promise<AsyncIterable<...>> that dispatches each Server-Sent Event by its event: name (via @azure/core-sse), deserializes the payload, and stops at the terminal event. Full heterogeneous multi-event dispatch and @terminalEvent handling are supported (named terminals keyed on the terminal flag; unnamed data: [DONE] sentinel terminals). Generation is driven by TCGC streamMetadata / sseMetadata.

Issues for the future:
#5660 #5659

Related pr to core for abort signal/canceling stream: Azure/azure-sdk-for-js#40238

…ault JSONL/SSE stream responses now return Promise<AsyncIterable<T>> of deserialized items/events instead of the raw binary Uint8Array body. JsonlStream<T> lazily decodes JSON Lines; SSEStream<T> dispatches each Server-Sent Event by its event: name (via @azure/core-sse), deserializes the payload, and stops at the terminal event. Heterogeneous multi-event dispatch and terminal-event handling are supported. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: de6a6ea9-d1f8-4a50-831f-d64d9f7cfa0d

Adds the workspace link entries for @typespec/streams, @typespec/sse and @typespec/events that were added to packages/typespec-ts/package.json for structured JSONL/SSE streaming. Required so CI's frozen-lockfile install matches package.json. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: de6a6ea9-d1f8-4a50-831f-d64d9f7cfa0d

github-actions · 2026-08-10T21:09:26Z

All changed packages have been documented.

✅ @azure-tools/typespec-ts

Show changes

`@azure-tools/typespec-ts` - feature ✏️

Generate structured JSONL and SSE streaming operations as Promise<AsyncIterable<T>> of deserialized items/events instead of raw binary Uint8Array bodies. Connection and modeled HTTP error validation are eager; payload deserialization is lazy. Generate streaming helpers only for supported MIME types and non-paging, non-LRO operations. Deserialize scalar SSE payloads into their declared client types. Dispatch unnamed discriminated SSE model variants by their payload discriminator and yield terminal payloads before stopping.,> ,> SSE uses the published @azure/core-sse createSseStream API. Close the SSE source before delivering a terminal payload, preserving the terminal item and reporting cleanup failures after yielding it.,> ,> JSONL decodes lines incrementally, flushes UTF-8 decoding at EOF, and cancels browser readers on early exit or decoding failures. Per-item deserialization uses existing TCGC serialization metadata.,> ,> Recognize standalone TypeSpec.Streams decorators in the shared test compiler and cover custom streams without incidental SSE imports.

Brings the branch up to date with upstream main so CI can build the PR merge commit. Resolves the conflict in pnpm-lock.yaml (took upstream and re-added the @typespec/streams, @typespec/sse and @typespec/events workspace links) and adapts the structured-streaming deserialize helper to the refactored getExceptionThrowStatement signature (now [string[], ServiceOperation]). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: de6a6ea9-d1f8-4a50-831f-d64d9f7cfa0d

github-actions · 2026-08-10T21:41:15Z

📦 Package size report

6 packages changed size, -836 B (-0.0%) packed overall.

Package	Packed (base → head)	Δ Packed	Unpacked (base → head)	Δ Unpacked
`@azure-tools/typespec-ts`	541.44 KB → 549.34 KB	+7.90 KB (+1.5%) 🔴	2.60 MB → 2.75 MB	+148.34 KB (+5.6%) 🔴
`@azure-tools/typespec-azure-portal-core`	42.48 KB → 36.26 KB	-6.22 KB (-14.6%) 🟢	193.20 KB → 242.62 KB	+49.43 KB (+25.6%) 🔴
`@azure-tools/azure-http-specs`	148.36 KB → 143.52 KB	-4.85 KB (-3.3%) 🟢	1.17 MB → 1.20 MB	+35.28 KB (+3.0%) 🔴
`@azure-tools/typespec-azure-examples`	65.86 KB → 62.45 KB	-3.40 KB (-5.2%) 🟢	261.37 KB → 308.13 KB	+46.76 KB (+17.9%) 🔴
`@azure-tools/typespec-autorest`	85.05 KB → 87.87 KB	+2.82 KB (+3.3%) 🔴	411.46 KB → 424.15 KB	+12.69 KB (+3.1%) 🔴
`@azure-tools/typespec-azure-core`	134.19 KB → 135.62 KB	+1.43 KB (+1.1%) 🔴	724.18 KB → 728.92 KB	+4.74 KB (+0.7%) 🔴

8 package(s) with no notable change

Package	Packed (base → head)	Δ Packed	Unpacked (base → head)	Δ Unpacked
`@azure-tools/typespec-client-generator-core`	243.03 KB → 243.95 KB	+944 B (+0.4%)	1.29 MB → 1.30 MB	+4.84 KB (+0.4%)
`@azure-tools/typespec-java`	13.51 MB → 13.51 MB	+254 B (+0.0%)	15.04 MB → 15.04 MB	+785 B (+0.0%)
`@azure-tools/typespec-go`	263.56 KB → 263.76 KB	+205 B (+0.1%)	1.35 MB → 1.35 MB	+1.82 KB (+0.1%)
`@azure-tools/typespec-azure-resource-manager`	184.05 KB → 184.13 KB	+90 B (+0.0%)	1.11 MB → 1.11 MB	+321 B (+0.0%)
`@azure-tools/typespec-python`	42.22 KB → 42.26 KB	+39 B (+0.1%)	164.91 KB → 165.08 KB	+175 B (+0.1%)
`@azure-tools/typespec-azure-rulesets`	5.50 KB → 5.50 KB	+10 B (+0.2%)	33.67 KB → 33.69 KB	+20 B (+0.1%)
`@azure-tools/typespec-autorest-canonical`	7.42 KB → 7.42 KB	—	26.00 KB → 26.00 KB	—
`@azure-tools/typespec-metadata`	15.91 KB → 15.91 KB	—	62.26 KB → 62.26 KB	—

_{Packed = gzipped .tgz published to npm. Unpacked = total extracted size. 🆕 added, 🗑️ removed. Packages from the core/ submodule are not included.
🔴 grew · 🟢 shrank — only changes of at least 512 B and 0.5% are marked.}

pkg-pr-new · 2026-08-10T21:43:42Z

Open in StackBlitz

npm i https://pkg.pr.new/@azure-tools/typespec-ts@5196

commit: 61202db

azure-sdk-automation · 2026-08-10T21:48:38Z

You can try these changes here

🛝 Playground	🌐 Website

Three fixes from a design review of the default JSONL/SSE structured streaming feature: 1. Split the SSE decoder into a separate sseStreamingHelpers.ts so JSONL-only packages no longer import (or need) @azure/core-sse. streamingHelpers.ts now contains only JSONL + shared helpers with no core-sse dependency. SseStreamingHelpers loads only when the package has an SSE operation, matching the @azure/core-sse dependency gate. 2. Only treat a constant SSE event as a terminal sentinel when isTerminalEvent is true. A non-terminal constant is a real payload variant and is now deserialized/yielded and included in the item type instead of silently terminating the stream. 3. Thread the event payloadContentType into each SSE descriptor and only JSON.parse JSON payloads; non-JSON (e.g. text/plain) payloads are passed through as the raw data string. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: de6a6ea9-d1f8-4a50-831f-d64d9f7cfa0d

Opt the http-specs streaming/sse scenario (unnamed, named+terminal, retrieve) into the typespec-ts integration suite so the default structured-streaming codegen is exercised end-to-end against the real spector mock. The generated public surface confirms the operations return Promise<AsyncIterable<T>> with heterogeneous per-event dispatch and terminal-event handling. JSONL is deferred from the integration baseline: its send() op exercises request-body (upload) stream typing, a pre-existing emitter gap unrelated to this response-streaming feature. JSONL response streaming remains covered by the unit-modular snapshot. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: de6a6ea9-d1f8-4a50-831f-d64d9f7cfa0d

Remove unrelated @typespec/http-client-python 0.35.1 churn from the lock and keep only the @typespec/events, @typespec/sse, and @typespec/streams workspace links required by typespec-ts's new streaming dependencies. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: de6a6ea9-d1f8-4a50-831f-d64d9f7cfa0d

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: de6a6ea9-d1f8-4a50-831f-d64d9f7cfa0d

Add @azure/core-sse devDependency (with clean lockfile entries) and a runtime integration test that exercises the generated SSE clients against the http-specs mock server: unnamed message events, heterogeneous named events with terminal [DONE] handling, and event-name-dispatched retrieve streaming. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: de6a6ea9-d1f8-4a50-831f-d64d9f7cfa0d

Move the @azure/core-sse version into the pnpm-workspace.yaml catalog and reference it via catalog: in package.json, matching the repo policy that all external dependencies use the catalog protocol. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: de6a6ea9-d1f8-4a50-831f-d64d9f7cfa0d

Merge jsonlStreaming.md, sseUnnamedStreaming.md, and sseNamedStreaming.md into a single streaming.md with three scenarios (the scenario runner splits each file on H1, so one file holds multiple scenarios). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: de6a6ea9-d1f8-4a50-831f-d64d9f7cfa0d

…turedStreamInfo Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: de6a6ea9-d1f8-4a50-831f-d64d9f7cfa0d

…ating Two structured-streaming correctness fixes: - Non-terminal SSE events whose payload needs no model deserializer (primitive/scalar/enum) were silently dropped because no deserialize callback was emitted. Emit an identity deserializer so the raw payload (JSON-parsed value, or raw string for non-JSON content) is yielded. Add a regression scenario mixing a model and a text/plain scalar event. - packageHasSseStreaming now mirrors getStructuredStreamInfo's gating (paging/LRO exclusions + streamMetadata & sseMetadata requirement) so @azure/core-sse is only injected when SSE streaming is actually generated. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: de6a6ea9-d1f8-4a50-831f-d64d9f7cfa0d

Maor Leger (maorleger)

This is coming along quite nicely!! Thanks so much for all the effort in getting this together.

I still have lots to review, but the overall direction seems ok. I noted a few findings that we should fix though

- Add streamingHelpers-browser.mts: uses asBrowserStream() and converts ReadableStream to AsyncIterable - Add streamingHelpers-react-native.mts: re-exports browser variant - Add sseStreamingHelpers-browser.mts: re-exports base (body already AsyncIterable) - Add sseStreamingHelpers-react-native.mts: re-exports browser variant - Fix terminal event name-aware matching in sseStreamingHelpers.ts (check descriptor by name first) - Add content-type validation for JSONL vs SSE stream detection - Add named event type discrimination for SSE return types (discriminated union) - Update streaming test baselines for named event discriminated unions - Clarify in SSE integration test that discriminated union enables type-safe narrowing Follows the same pattern as get-binary-response polyfills. Enables: - Node.js: StreamableMethod.asNodeStream() → AsyncIterable (default) - Browser: StreamableMethod.asBrowserStream() → ReadableStream → AsyncIterable - React-Native: Same as browser (browser APIs available) Addresses PR review comments: - r3815393091: Environment polyfills - r3815434566: Content-type validation - r3815531940: Terminal event name-aware matching - r3815653900: Named event type discrimination with discriminated union Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5de9bff8-f217-4c66-9e30-bdc80256fed8

Include the SSE event name when JSON payload parsing fails and preserve the original error as the cause. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5de9bff8-f217-4c66-9e30-bdc80256fed8

Generate discriminated union return types for heterogeneous named SSE streams so callers can narrow payloads by event name. Update streaming operation baselines. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 5de9bff8-f217-4c66-9e30-bdc80256fed8

…ed events in an envelope Terminal events are now always consumed internally and never yielded, so the declared item union is sound by construction. The terminal check runs after descriptor resolution by event name (an unrelated event carrying the sentinel data can no longer end the stream) and before deserialization (terminal payloads are never yielded). Named SSE events are wrapped in a { event, data } envelope so the generated return type matches what the runtime helper yields. The envelope is applied all-or-nothing via everyPayloadEventIsNamed to avoid a union mixing envelope and bare shapes. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: de6a6ea9-d1f8-4a50-831f-d64d9f7cfa0d

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: de6a6ea9-d1f8-4a50-831f-d64d9f7cfa0d

Use ordinary JSON.stringify quoting instead of custom script-embedding escapes. Remove the dedicated utility and exotic-metadata tests while preserving SSE Spector coverage. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8bbec15a-04ed-41e4-9fae-e27932b80317

Include terminal constants in generated return types and yield them before stopping. Preserve named event envelopes with the default message name for unnamed terminals, keep unnamed streams payload-only, and update runtime, snapshots and Spector coverage. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8bbec15a-04ed-41e4-9fae-e27932b80317

Libba Lawrence (l0lawrence) · 2026-10-07T19:55:34Z

+      const yielded = useEventEnvelope
+        ? `({ event: ${JSON.stringify(event.eventName ?? "message")}, data: ${event.deserializeExpression} })`
+        : event.deserializeExpression;
+      parts.push(`deserialize: (data) => ${yielded}`);


I don't think this will be an issue?

Copilot

🟡 Changes recommended

Critical browser SSE cleanup and scalar deserialization issues remain, along with JSONL gating and breaking-release metadata corrections.

3 open findings

Scalar SSE payloads are emitted as strings instead of declared types · New
Browser SSE streams fail cleanup after terminal events · New
Browser SSE iteration rejects after terminal event cleanup · New

13 resolved since last review

Deserialize scalar SSE payloads instead of returning raw strings
Regenerate lockfile to satisfy the @azure/core-sse version range
Handle unnamed SSE frames with the fallback descriptor
Fix browser helper import to resolve the emitted JavaScript module
Replace nonexistent SseStream type in generated SSE helper
Replace nonexistent SseStream type in browser helper
Use an available SSE stream API or implement reconnecting wrapper
getStreamResponse leaves result.body as an AsyncIterable, but getExceptionThrowStatement…
This path ignores sseEvent.isEventEnvelope and deserializes payloadType directly. For an event…
The PR adds substantial JSONL decoding logic (line splitting, buffering across chunks, JSON.parse…
On early termination (for example, after an SSE terminal event), this generator's finally only…
An omitted payloadContentType is not always JSON: TCGC leaves it undefined for inferred event…
The new JSONL decoder has no runtime unit or integration coverage; the added helper tests exercise…

Files not reviewed (1)

pnpm-lock.yaml: Generated file

🧠 Review effort: Lite

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8bbec15a-04ed-41e4-9fae-e27932b80317

Copilot

🔵 Needs a closer look

Browser SSE terminal cleanup fails with the pinned dependency, and structured-stream response aliases are misleading.

0 open findings

3 resolved since last review

Browser SSE iteration rejects after terminal event cleanup
Browser SSE streams fail cleanup after terminal events
Scalar SSE payloads are emitted as strings instead of declared types

Files not reviewed (1)

pnpm-lock.yaml: Generated file

🧠 Review effort: Lite

Jeremy Meng (jeremymeng) · 2026-10-08T17:58:06Z

+  event: EventMessage,
+  descriptors: SseEventDescriptor<T>[],
+): SseEventDescriptor<T> | undefined {
+  if (event.event) {


can event.event be empty string? Other falsy values would also reach the else block.

we initialize it to be "" so yes it can be that gets treated as eventType "message"

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8bbec15a-04ed-41e4-9fae-e27932b80317

…tream on terminal event Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8bbec15a-04ed-41e4-9fae-e27932b80317

Jialin Huang (JialinHuang803) · 2026-10-13T01:16:01Z

+  - "@azure-tools/typespec-ts"
+---
+
+Generate structured JSONL and SSE streaming operations as `Promise<AsyncIterable<T>>` of deserialized items/events instead of raw binary `Uint8Array` bodies. Connection and modeled HTTP error validation are eager; payload deserialization is lazy. Generate streaming helpers only for supported MIME types and non-paging, non-LRO operations. Deserialize scalar SSE payloads into their declared client types. Dispatch unnamed discriminated SSE model variants by their payload discriminator and yield terminal payloads before stopping.


The content here will be shown in the changelog once a new version is released. I suggest that we make it shorter.

Jialin Huang (JialinHuang803) · 2026-10-13T01:52:04Z

+              ? event.deserializeExpression
+              : String(sseEvent.payloadType.value);
+        }
+      } else {


Is it possible that an event be nullable (sseEvent.payloadType.kind === "nullable")? For example:

model Payload { @encodedName("application/json", "wire_value") value: string; timestamp: utcDateTime; } @events union NullableEvents { @Events.contentType("application/json") update: Payload | null, } @route("/receive") op receive(): SSEStream<NullableEvents>;

The current deserializing behavior is

deserialize: (data) => ({ event: "update", data: data === null ? null : data, // <- should be payloadDeserializer(data) }),

I think we should still use the deserializer if data is not null.

Let me verify but I don't think there is a linter preventing it and if the wire data could be data: null

Jialin Huang (JialinHuang803) · 2026-10-13T02:03:48Z

+    isAsync: true,
+    isExported: true,
+    name,
+    propertyName: normalizeName(operation.name, NameType.Property),


propertyName names the public method on the client or operation group, and it should come from getOperationName as well, like name. Otherwise, a method annotated with @clientName(exact("my_operation")) will become myOperation at the client level.

Jialin Huang (JialinHuang803) · 2026-10-13T03:00:42Z

+    throw createRestError(result);
+  }
+
+  const contentType_1 = Object.entries(response.headers)


Just curious, why is it contentType_1, not contentType?

there was a contentType in here already so defautled to _1 - let me see about rename

Jialin Huang (JialinHuang803) · 2026-10-13T03:15:31Z

+    } else if (descriptor.discriminator) {
+      discriminated.push(descriptor);
+    } else {
+      fallback ??= descriptor;


If variants are unnamed, nonterminal constants, like below:

@events union ConstantEvents { @Events.contentType("text/plain") "cat", @Events.contentType("text/plain") "dog", } @route("/receive") op receive(): SSEStream<ConstantEvents>;

The generated descriptors would be:

[ { isTerminal: false, deserialize: () => "cat", contentType: "text/plain" }, { isTerminal: false, deserialize: () => "dog", contentType: "text/plain" }, ]

Will runtime fallback to the first descriptor no matter the response is "cat" or "dog"?

it would, can add something to check for value to avoid that? right now I dont believe search uses unnamed events at all so we shouldn't run into this scenario yet at least

Jialin Huang (JialinHuang803) · 2026-10-13T05:20:01Z

+    ?.split(";", 1)[0]
+    .trim()
+    .toLowerCase();
+  if (contentType !== "text/event-stream" || !response.body) {


If the operation is declared like

@route("/receive") op receive(): SSEStream<MessageEvents> | NoContentResponse;

which has a streaming response and a 204 response, will an error be thrown if response.body is empty which is not expected?

ohh I think it would, let me fix that

Libba Lawrence (l0lawrence) mentioned this pull request Aug 10, 2026

feat(typespec-ts): generate structured JSONL and SSE streaming by default l0lawrence/typespec-azure#1

Closed

microsoft-github-policy-service Bot added the emitter:typescript Issues for @azure-tools/typespec-ts emitter label Aug 10, 2026

Libba Lawrence (l0lawrence) changed the title ~~feat(typespec-ts): generate structured JSONL and SSE streaming by default~~ feat(typespec-ts): streaming Aug 10, 2026

github-actions Bot mentioned this pull request Aug 11, 2026

[docs-sync] Update documentation for recent code changes XiaofeiCao/typespec-azure#68

Draft

Libba Lawrence (l0lawrence) and others added 7 commits August 11, 2026 10:06

Merge branch 'main' of https://github.com/Azure/typespec-azure into HEAD

defc091

style: fix prettier formatting in SSE streaming snapshots

f4a1859

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: de6a6ea9-d1f8-4a50-831f-d64d9f7cfa0d

Libba Lawrence (l0lawrence) commented Aug 18, 2026

View reviewed changes

Comment thread packages/typespec-ts/spector.config.yaml

Libba Lawrence (l0lawrence) and others added 3 commits August 18, 2026 10:32

docs(typespec-ts): drop redundant default-behavior note from getStruc…

d800ce5

…turedStreamInfo Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: de6a6ea9-d1f8-4a50-831f-d64d9f7cfa0d

Maor Leger (maorleger) reviewed Aug 19, 2026

View reviewed changes

Libba Lawrence (l0lawrence) force-pushed the l0lawrence-vigilant-system branch from c503c07 to 1a2adc2 Compare August 19, 2026 21:17

Libba Lawrence (l0lawrence) and others added 3 commits August 19, 2026 14:41

github-advanced-security Bot found potential problems Aug 19, 2026

View reviewed changes

Comment thread packages/typespec-ts/src/modular/helpers/operation-helpers.ts Fixed

wip terminal event

4b39604

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: de6a6ea9-d1f8-4a50-831f-d64d9f7cfa0d

Libba Lawrence (l0lawrence) commented Oct 7, 2026

View reviewed changes

Comment thread packages/typespec-ts/test/azure-modular-integration/streaming-sse.test.ts

Libba Lawrence (l0lawrence) and others added 2 commits October 7, 2026 09:34

github-advanced-security Bot found potential problems Oct 7, 2026

View reviewed changes

Libba Lawrence (l0lawrence) requested a lite review from Copilot October 7, 2026 19:41

Copilot started reviewing on behalf of Libba Lawrence (l0lawrence) October 7, 2026 19:42 View session

Copilot AI reviewed Oct 7, 2026

View reviewed changes

Comment thread packages/typespec-ts/src/modular/helpers/operation-helpers.ts

Comment thread packages/typespec-ts/src/modular/helpers/operation-helpers.ts

Comment thread packages/typespec-ts/static/static-helpers/sseStreamingHelpers.ts Outdated

Fix SSE scalar payload deserialization

414f1bd

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8bbec15a-04ed-41e4-9fae-e27932b80317

Libba Lawrence (l0lawrence) requested a lite review from Copilot October 7, 2026 20:48

Copilot started reviewing on behalf of Libba Lawrence (l0lawrence) October 7, 2026 20:50 View session

Copilot AI reviewed Oct 7, 2026

View reviewed changes

Jeremy Meng (jeremymeng) reviewed Oct 8, 2026

View reviewed changes

Libba Lawrence (l0lawrence) and others added 2 commits October 8, 2026 11:10

Fix unnamed SSE model discriminator dispatch

f09970d

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8bbec15a-04ed-41e4-9fae-e27932b80317

wip comment address

4cba8ca

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8bbec15a-04ed-41e4-9fae-e27932b80317

This was referenced Oct 9, 2026

refactor sse in typespec-ts #5659

Open

typespec-ts reconnect support not present, requires work if there is service demand #5660

Open

Libba Lawrence (l0lawrence) marked this pull request as ready for review October 12, 2026 16:12

Libba Lawrence (l0lawrence) requested review from Jialin Huang (JialinHuang803), Mary Gao (MaryGao), Mark Cowlishaw (markcowl), Qiaoqiao Zhang (qiaozha), Timothee Guerin (timotheeguerin) and Jeff Fisher (xirzec) as code owners October 12, 2026 16:12

found when testing against azure search need to yield after closing s…

61202db

…tream on terminal event Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8bbec15a-04ed-41e4-9fae-e27932b80317

Jialin Huang (JialinHuang803) reviewed Oct 13, 2026

View reviewed changes

Conversation

Libba Lawrence (l0lawrence) commented Aug 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What is generated

Uh oh!

github-actions Bot commented Aug 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

@azure-tools/typespec-ts - feature ✏️

Uh oh!

github-actions Bot commented Aug 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📦 Package size report

Uh oh!

pkg-pr-new Bot commented Aug 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

azure-sdk-automation Bot commented Aug 10, 2026

Uh oh!

Uh oh!

Maor Leger (maorleger) left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

🟡 Changes recommended

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

🔵 Needs a closer look

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Libba Lawrence (l0lawrence) Oct 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Jialin Huang (JialinHuang803) Oct 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Libba Lawrence (l0lawrence) Oct 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Libba Lawrence (l0lawrence) Oct 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Libba Lawrence (l0lawrence) commented Aug 10, 2026 •

edited

Loading

github-actions Bot commented Aug 10, 2026 •

edited

Loading

`@azure-tools/typespec-ts` - feature ✏️

github-actions Bot commented Aug 10, 2026 •

edited

Loading

pkg-pr-new Bot commented Aug 10, 2026 •

edited

Loading

Libba Lawrence (l0lawrence) Oct 8, 2026 •

edited

Loading

Jialin Huang (JialinHuang803) Oct 13, 2026 •

edited

Loading

Libba Lawrence (l0lawrence) Oct 13, 2026 •

edited

Loading

Libba Lawrence (l0lawrence) Oct 13, 2026 •

edited

Loading