Allow sending events from within an FSM state function #1664
Assignees
Comments
Open
|
Confirmed with Moe, this is not a blocker for the current deadline anymore, they are using pub sub instead of FSM to get around this. |
github-merge-queue bot
pushed a commit
that referenced
this issue
Aug 15, 2024
closes #1664 closes #2334 This is particularly useful when an FSM state itself knows which state it should be in next, for example transitioning a payment to "voided" if an error occurs communicating with an external vendor. - Adds `fsm.Next(ctx, event)` to the go runtime - Only one next transition is allowed per fsm instance - When a transition completes, the next transition is queued up if it exists - When a transition returns an error, we wipe the next transition so that the retry attempt can set the next transition again In another PR we will move away from using `ftl.Next()` to avoid the reference cycle issue. --------- Co-authored-by: Matt Toohey <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, sending an event to an FSM while the FSM is transitioning is invalid. However, sometimes the state itself knows what the next state should be.
We could either allow
Send()to be used in this fashion directly, or add a new methodNext()that fulfils this need.fsm -> funcs -> fsm.Next()The text was updated successfully, but these errors were encountered: