Skip to content

Fix SignalR push and client compatibility - #15

Merged
mamonth merged 1 commit into
mainfrom
fix/signalr-push-and-client-compat
Sep 9, 2026
Merged

mamonth merged 1 commit into
mainfrom
fix/signalr-push-and-client-compat

Conversation

@mamonth

@mamonth mamonth commented Sep 9, 2026

Copy link
Copy Markdown
Owner
  • Accept the record-separator-terminated SignalR handshake (@microsoft/signalr framing) while keeping the bare form
  • Widen async-message and example payloads to any JSON value; arrays and scalars pass through verbatim
  • Resolve add-example targets against SignalR hub channels and enforce the protocol discriminator on the hub fallback
  • Expose the per-account upgrade path in connection context and consumer metadata (RS.SHR.26, RS.AMG.32, RS.MAPI.39)
  • Refactor consumer-record construction onto a single atomic registry snapshot; extract shared SignalR test helpers
  • Align OpenAPI contract, specs, and docs; archive the OpenSpec change

- Accept the record-separator-terminated SignalR handshake
  (@microsoft/signalr framing) while keeping the bare form
- Widen async-message and example payloads to any JSON value; arrays
  and scalars pass through verbatim
- Resolve add-example targets against SignalR hub channels and enforce
  the protocol discriminator on the hub fallback
- Expose the per-account upgrade path in connection context and
  consumer metadata (RS.SHR.26, RS.AMG.32, RS.MAPI.39)
- Refactor consumer-record construction onto a single atomic registry
  snapshot; extract shared SignalR test helpers
- Align OpenAPI contract, specs, and docs; archive the OpenSpec change
@mamonth
mamonth merged commit 241ac65 into main Sep 9, 2026
7 checks passed
@mamonth
mamonth deleted the fix/signalr-push-and-client-compat branch September 9, 2026 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant