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
I've mentioned it in another issue, but only now tested it separately and making an issue of its own. When state machine is created and its initial state configuration is entered, no entry actions are called. Example:
When ran, program shows nothing - asserts confirm that state machine entered desired configuration (ss1(ss1_1)), but entry actions were not called. Since entry actions set identity for states, machine will have not been initialized properly.
Introducing a dummy initial state and anonymous transition helps:
I think action order is still incorrect (see #43), but states are initialized at least. It's not intuitive and error prone though, takes running into the bug to resort to the dummy state.
The text was updated successfully, but these errors were encountered:
I've mentioned it in another issue, but only now tested it separately and making an issue of its own. When state machine is created and its initial state configuration is entered, no entry actions are called. Example:
When ran, program shows nothing - asserts confirm that state machine entered desired configuration (
ss1(ss1_1)
), but entry actions were not called. Since entry actions set identity for states, machine will have not been initialized properly.Introducing a dummy initial state and anonymous transition helps:
Output:
I think action order is still incorrect (see #43), but states are initialized at least. It's not intuitive and error prone though, takes running into the bug to resort to the dummy state.
The text was updated successfully, but these errors were encountered: