Access to firing event in callbacks #168
Comments
|
Having access to the name of the event would fix #159 too. |
alto
added a commit
that referenced
this issue
Sep 12, 2014
|
I just released version Take a look at the README: The current event triggeredWhile running the callbacks you can easily retrieve the name of the event triggered # taken the example callback from above
def do_something
puts "triggered #{aasm.current_event}"
endand then job = Job.new
# without bang
job.sleep # => triggered :sleep
# with bang
job.sleep! # => triggered :sleep!Please, let me know if that solves this issue! |
|
This is perfect, thank you for the work and quick turnaround! ❤️ |
|
That is awesome! The issue has been solved =) Thank you so much for the effort. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There does not seem to be a way to access the name of the event that triggered an on_transition callback. We need this for a pubsub to record state changes event (because externally we care about triggered events and internally we care about states). In this case the to_state/from_state is not helpful, we need the particular event. There are a number of ways to hack this in our application and all of them are gross.
This would be a very helpful attribute in our case.
I looked into it a bit and it doesn't seem too hard to add
:current_eventtoInstanceBasebut the spec tests do not run (an rspec error) and I don't want to have to set up Mongo (why not sqlite?) and debug them to figure it out.Thanks for the great state machine gem.
The text was updated successfully, but these errors were encountered: