When used with ActiveRecord, AASM does not check that fields are in the backing db

[michaeldickens]

I recently encountered a bug in some code I wrote where I was attempting to access an AASM state from the backing database associated with an ActiveRecord. I hadn't migrated the database, so AASM couldn't find the column in the database. Instead of returning a helpful error, it said, NoMethodError: undefined methodtype' for nil:NilClass. I discovered that this happens in active_record_persistence.rb:131 whenself.class.columns_hash[self.class.aasm_column.to_s].typecallstypeon anil` value. It would be helpful if AASM checked that the field was in the database before trying to operate on it.

[fabioperrella]

@alto I can try to do this. What branch should I use?

[alto]

@fabioperrella ?

[fabioperrella]

@alto I was looking for some issue to contribute, if you want, I will try to send you a pull request. I asked in what branch should I work on it ?

[alto]

@fabioperrella Ah, now I understand. There are two main branches currently worked on, master and multiple_state_machines_per_class. I would recommend to branch from master, because the multiple one is changing quite a lot.

Thanks for your help. I really appreciate this!

[fabioperrella]

@michaeldickens I tryed to reproduce your error but I couldn't. I created a class using aasm and didn't migrated the DB (the column aasm does not exist), then when I called the method .aasm_state, it raised the error NoMethodError: undefined method `aasm_state' for #<Account id: nil, name: "aa">
I used the last stable version of aasm (4.2.0) and rails 4.2.3
Which versions were you using?

[alto]

@michaeldickens I just released version 4.6.0 including @anilmaurya's patch. Please re-open if it doesn't work.