Transition to initial state should trigger callbacks.

[kjwierenga]

Is the initial pseudo state implicit? I think it would be wise to have a way to initiate the transition into the first state with an explicit call to initial!.

require 'finite_machine'

phone = FiniteMachine.define do
  initial :first

  callbacks {
    on_before { |event| puts "event #{event.name}" }
    on_enter(:first) { |event| puts "transition #{event.name} #{event.from} -> #{event.to}" }
  }
end

phone.start!

This would produce output:

event start!
transition INITIAL -> first

This initial transition could also be done as the last step in define but by having an explicit start! call the user has some control over when the initial transition is triggered.

Does this make sense?

[piotrmurach]

This should already work, the initial docs describes your case I think. Basically if you pass defer: true to initial, this will allow you to call the init event later on. Also by setting the event as deffered the very start state will be set to :none and thus transition :none => :first. Is that what you have in mind?

[kjwierenga]

Ah, I forgot that. You’re absolutely right. But, if you don’t specify defer: true, then the initial transition doesn’t trigger callbacks. A small inconsistency?

Op 26 mei 2014, om 22:51 heeft Piotr Murach notifications@github.com het volgende geschreven:

This should already work, the initial docs describes your case I think. Basically if you pass defer: true to initial, this will allow you to call the init event later on. Also by setting the event as deffered the very start state will be set to :none and thus transition :none => :first. Is that what you have in mind?

—
Reply to this email directly or view it on GitHub.

[kjwierenga]

Nice work.