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
The toState variable holds a reference to the actual state the state machine will transition to (after pseudo states transitions are followed), whereas the state variable holds a reference to the destination state before following pseudo states transitions.
The text was updated successfully, but these errors were encountered:
Hmm, for quick look you may be right about this. There's been no real use of post stage internally so this may have slipped from any existing tests. I'll try to poke around more to create some new tests.
Let's say I have a state machine with the following structure :
And I configure an Interceptor that looks just like this:
Depending on what the guard function returns, the following paths are possible :
Initial State --> "Choice_State" -> "One"
The interceptor prints the following info:
Initial State --> "Choice_State" -> "Default"
The interceptor prints the following info:
In both cases, I expected the postStateChangeInterceptor to show the same state as the preState interceptor.
I believe the culprit is the following call in
AbstractStateMachine::switchToState
:When it should be
The
toState
variable holds a reference to the actual state the state machine will transition to (after pseudo states transitions are followed), whereas thestate
variable holds a reference to the destination state before following pseudo states transitions.The text was updated successfully, but these errors were encountered: