Machine.addHandler(transition: order: handler:) -> Disposable not working ? about swiftstate HOT 6 CLOSED

In your example, you are registering event-based routes but attaching state-based handler, so it doesn't react to any event-triggering.

To fix this, please replace:

// register handler for state-based transition, e.g. `machine <- .State0`
machine.addHandler(.Any => .Any) { ... }

to:

// register handler for event-based transition, e.g. `machine <-! .Event0`
machine.addHandler(event: .Event0) { ... }

from swiftstate.

I thought it was working in previous version, though ?

from swiftstate.

Yes, previous ver 3.x was working in that way (equal to addEventHandler()).
From ver 4.0.0, you need to use machine.addHandler(event:) instead.

P.S.
For reacting to any events, you can use machine.addHandler(event: .Any).

from swiftstate.

Updated README.md in 84d4b42.

from swiftstate.

👏
I see that. Thanks !

from swiftstate.

Hello.

I find this behavior surprising. I was just playing with SwiftState, and wanted to model the state machine using a mix of events and states. The idea being that I would attach handlers to the states, but send events to the machine to transition.

I understand this is not possible—I would have to choose events or states, but not both.

from swiftstate.