callback order about finite_machine HOT 4 CLOSED

Thanks Klaas! This looks so much nicer now and provides proper callback ordering. 😍

fsm = FiniteMachine.define do
  initial :previous

  events {
    event :go, :previous => :next, if: -> { puts "checking condition"; true }
  }

  callbacks {
    on_exit       { |event| puts "exit_#{event.from}" }
    on_before     { |event| puts "\tbefore_#{event.name}"    }
    on_transition { |event| puts "\t\ttransition: #{event.name}: #{event.from} -> #{event.to}" }
    on_enter      { |event| puts "\tenter_#{event.to}"  }
    on_after      { |event| puts "after_#{event.name}"     }
  }
end

from finite_machine.

Cool. Good job.

Op 26 mei 2014, om 20:56 heeft Piotr Murach [email protected] het volgende geschreven:

Thanks Klaas! This looks so much nicer now and provides proper callback ordering.

fsm = FiniteMachine.define do
initial :previous

events {
event :go, :previous => :next, if: -> { puts "checking condition"; true }
}

callbacks {
on_exit { |event| puts "exit_#{event.from}" }
on_before { |event| puts "\tbefore_#{event.name}" }
on_transition { |event| puts "\t\ttransition: #{event.name}: #{event.from} -> #{event.to}" }
on_enter { |event| puts "\tenter_#{event.to}" }
on_after { |event| puts "after_#{event.name}" }
}
end
—
Reply to this email directly or view it on GitHub.

from finite_machine.

Updated docs to explain the callback lifecycle. see

from finite_machine.

@kjwierenga Released 0.7.0 version! I will soon post more issues/milestone for future ideas/features that I'd like to discuss.

from finite_machine.