'Event' naming collision

[alexhanh]

I have an Event model in my Rails project and I do this:

  def event_fired(current_state, new_state, event)
    Event.create!(type: "s.#{event}", transfer: self)
  end

with this, it throws undefined method 'create!' for Transitions::Event:Class. It seems it tries to use Transitions::Event instead of my Event model.

Is there any clean way to fix this?

[alexhanh]

I found two ways so far:

1. Define the relationship before including Transitions

  has_many :events
  include ActiveModel::Transitions

2. Use a namespace for the model

Would love to hear your input.

[troessner]

1. Define the relationship before including Transitions

I think that's a bad hack like everything that relies on ordering. But you probably agree with that already.:)

2. Use a namespace for the model

I think that's better but still not optimal.

You can do:

  def event_fired(current_state, new_state, event)
    ::Event.create!(type: "s.#{event}", transfer: self)
  end

I just tested it and this works for me. Also, I think this is the ruby-idiomatic way of solving this problem.

Let me know if this works for you and what you think of this solution, then I'll update the README to make this easier for others in the future.

[alexhanh]

Ahh, I didn't know you could refer to the top-level Event object in the namespace in that way, that's neat! Thanks for the help!

[troessner]

Addendum: I updated the README to make this clearer to everybody: 883dc00