Skip to content

Clarify the language on INotificationHandler in Wolverine #1521

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
Jun 27, 2025
Merged

Clarify the language on INotificationHandler in Wolverine #1521

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/introduction/from-mediatr.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@ which is just not suitable if you need delivery guarantees of that work. Wolveri
with its in memory, local queues such that work will *not* be lost in the case of errors. Moreover, using the Wolverine local queues
allows you to take advantage of Wolverine's error handling capabilities for a much more resilient system that you'll achieve with MediatR.

`INotificationHandler` in Wolverine is just a message handler. You can publish messages anytime through the `IMessageBus.PublishAsync()` API, but if you're just
The equivalent of `INotificationHandler` in Wolverine is just a message handler. You can publish messages anytime through the `IMessageBus.PublishAsync()` API, but if you're just
needing to publish additional messages (either commands or events, to Wolverine it's all just a message), you can utilize Wolverine's
[cascading message](/guide/handlers/cascading) usage as a way of building more testable handler methods.

Expand Down