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
It would be nice if the state machine could allow for multiple side effects on an transition. For example one (always used) side effect of logging the transition and one highly specialized for the stateA ---> stateB transition (caused by eventC)
I image the call site to look something like this:
To also allow the old style of only specifying one side effect it seems like I would need to overload StateMachine.StateDefinitionBuilder.transitionTo() and dontTransition()
I would be happy to try this (given some pointers on where to start).
The text was updated successfully, but these errors were encountered:
It seems like the way to solve this in this lbirary is to put the general case in onTransition before then matching to the actual side effeect and doing the specific action
It would be nice if the state machine could allow for multiple side effects on an transition. For example one (always used) side effect of logging the transition and one highly specialized for the
stateA ---> stateB
transition (caused byeventC
)I image the call site to look something like this:
To also allow the old style of only specifying one side effect it seems like I would need to overload
StateMachine.StateDefinitionBuilder.transitionTo()
anddontTransition()
I would be happy to try this (given some pointers on where to start).
The text was updated successfully, but these errors were encountered: