Sagas from HTTP endpoints New in 1.10.0
Starting and driving Wolverine sagas from Wolverine.HTTP endpoints — why the first return value is the response body and a Saga must therefore be a later tuple member, the [EmptyResponse] shape and the static Start() it silently skips, why an endpoint sends rather than handles when continuing a saga, choosing a status code for a saga that no longer exists, and testing a saga-starting endpoint with Alba when its timeout is scheduled.
Use when a web request begins a long-running workflow, or a saga-starting endpoint returns the wrong body or skips its side effects.
Skill details
- Skill name:
wolverine-http-sagas - Applies to:
wolverine - Tags:
wolverine,http,sagas,workflow,endpoints,testing - Added in: 1.10.0
- License: Proprietary. Copyright JasperFx Software LLC.