State-based outputs and message routing - #4
Open
chris-cald wants to merge 2 commits into
Open
chris-cald wants to merge 2 commits into
chris-cald wants to merge 2 commits into
Conversation
added 2 commits
May 1, 2018 16:54
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In using the state machine node I found that I was always creating a switch node to handle each state differently. Rather than continuing this repetitive and error-prone practice (the switch states were an exact copy of the SM states and text needed to be updated in both if the name of the state changed), I incorporated the concept of state-based message routing into the state machine node itself. Feel free to change text as you see appropriate.