-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension.EnteredInitialState has context.State == null #33
Comments
Use the state passed to the method directly. The state of the context is the source state, which is null in case of initialization. Does this work for you? |
No, sorry, I need the IState, because I need to get the valid triggers. |
I see. That can be accomplished by changing the code in the method If you want the change quickly, I suggest you change the code as explained above and compile the state machine on your own. Otherwise, you'll have to wait for me and my time is very limited at the moment. See http://www.appccelerate.com/howtocontributewalkthrough.html for an explanation how to get your own nuget package easily from our build infrastructure through a pull request. I hope that helps. |
Maybe it might be useful to add a property containing the target state? My assumption was that the context state always contains the target state for all transitioned/initialized events. |
This prevents getting the
IState<TState, TEvent>
of the initial status.Example extension code:
The text was updated successfully, but these errors were encountered: