State Machine Definition Intantiates Half-Loaded Class about transitions

[troessner]

Hmmm, i see your problem - let me check what we can do about this.

[troessner]

I really hate it when gems just override methods without telling you. But on second thought i think that this check is indeed pointless since most people will define the state machine at the top of the file rendering this check useless.
I'd say we remove it alltogether - what do you think?

[bnmrrs]

I'm +1 on just removing it, not super useful in the current implementation.

[troessner]

I will remove it in the next couple of days - currently I am travelling without my oh so precious ssh keys or a laptop for that matter..:)

[psycotica0]

If you're good with it, I think that'd be the best solution.
Thanks.

[jwo]

I know you said you'd remove... Just want to document a use case that I had with this in case you implement a different way:

I'm having trouble with loading a schema in Rails because of this as well. If I delete out the database (or try to use in memory, or change to another DB), then:

When I load the schema or run rake db:migrate

1. it loads model definitions
2. Which includes ActiveModel::Transitions
3. Which of executes machine.klass.new.respond_to?(method_name)
4. Which connected to DB to check if "state" is defined there
5. which fails because the table doesn't exist yet

It works when adding to a model that already exists, just not a brand new setup. Rails 3.2.6

[troessner]

@jwo thanks, all the more reason to remove this check.

FYI @ALL I removed this feature and released version 1.0.1.

Thanks everybody!