Skip to content

Fix small typo #1803

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jeremydmiller merged 1 commit into from
Nov 4, 2025
Merged

Fix small typo #1803

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/guide/messaging/transports/signalr.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Much of the sample code is taken from a runnable sample application in the Wolve
:::

The [SignalR library](https://dotnet.microsoft.com/en-us/apps/aspnet/signalr) from Microsoft isn't hard to use from Wolverine for simplistic WebSockets
or Server Side Events usage , but what if you want a server side
or Server Side Events usage, but what if you want a server side
application to exchange any number of different messages between a browser (or other WebSocket client because that's
actually possible) and your server side code in a systematic way? To that end, Wolverine now supports a first class messaging transport
for SignalR. To get started, just add a Nuget reference to the `WolverineFx.SignalR` library:
Expand Down