Closed kingdonb closed 4 years ago
Since "Conditional transitions" feature, there can be multiple event definitions with the same name for the same state like in https://github.com/geekq/workflow#conditional-event-transitions.
Will update the example and will ensure only working example code goes to the readme. Already started switching README to asciidoctor for that.
That's a good reason, thank you for weighing in. Makes sense to me now. (Closing)
I was reading the documentation under Accessing your workflow specification
Example 1 shows:
I tried this with my workflow object and I had to modify it slightly to get it to work. The output I got is below:
I couldn't think of any good reason why events[:key] should return an array. An event can only cause a transition to a single state, right? So I think this is actually a bug in the software, not in the documentation. If there is a reason I did not see, I'm all ears.
Could you weigh in on whether you returned an array here on purpose, or not?