Skip to content

Update sagas.md #534

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
Sep 11, 2023
Merged

Update sagas.md #534

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
4 changes: 2 additions & 2 deletions docs/guide/http/sagas.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,8 +60,8 @@ public static (

Remember in Wolverine.HTTP that the *first* return value of an endpoint is assumed to be the response body by Wolverine, so if you are
wanting to start a new saga from an HTTP endpoint, the `Saga` return value either has to be a secondary value in a tuple to
opt into the Saga mechanics. Alternatively, if all you want to do is start a new saga, but nothing else, you can return
the `Saga` type *and* force Wolverine to use the return value as a new `Saga` like so:
opt into the Saga mechanics. Alternatively, if all you want to do is *create* a new saga, but nothing else, you can return
the `Saga` type *and* force Wolverine to use the return value as a new `Saga` as shown in the snippet below. Please note that when creating a `Saga` entity in this manner, if it has a static `Start()` method, it will not be invoked. Other message handlers in the `Saga` will behave as usual.

snippet: sample_start_saga_from_http_endpoint_empty_body