You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Keep OnFault as the name for saga fault transitions
An earlier commit on this branch renamed OnFault to OnReplyFault because it
only covers fault replies. That encoded a coverage gap into the name.
The extensions layer names concepts over the channel-level primitives of the
core descriptor: OnTimeout is OnRequest<SagaTimedOutEvent> and is not called
OnRequestTimeout. OnFault belongs to that vocabulary, and not covering publish
is a missing feature rather than a naming boundary.
The narrower name also survives neither plausible future. If publish faults are
delivered as a NotAcknowledgedEvent on the reply endpoint, the same route and
the same transition catch them and OnReplyFault becomes too narrow. If fan-in
semantics warrant a separate hook, the symmetric pair is OnSendFault and
OnPublishFault, where a channel name sits oddly beside a verb name.
The scope is documented instead. Neither a failing subscriber of a published
event nor a failing saga transition produces a reply, so neither reaches this
transition, and the summary now says so.
This removes the public API rename from the branch: OnFault keeps the signature
it has on main, and only its body and documentation change.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
0 commit comments