-
Notifications
You must be signed in to change notification settings - Fork 510
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build new object through an association doesn't trigger the state_machine's initial lambda #314
Comments
It looks to me like this is no longer working for new in Rails 4.2 Rails 4.2:
Rails 4.0
Note that I didn't have the problem with building through an association, but I'm on a fork. |
I've the same problem with Rails 4.2. Have you found a fix or a working fork? |
running into this as well, hopefully this can be fixed and the gem maintained again at some point |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey guys, I am using the latest version of
state_machine
. Today I found a problem that my state_machine doesn't trigger the state_machine's:initial
lambda codes if I build objects through an association, but does if I useOrder.new
.There are two models,
Creator
andOrder
, in my application, and there is a has_many association from a creator to many orders. The below shows the definition of my state_machine for Order:The result of building order by the
new
class method:Well, it goes well as what I expect, but, if I build a new order by a creator, it will have something wrong:
See? Both built orders have
creator_id
, but have opposite state.Then I add breakpoint to the lambda, I found that the lambda will be run if I build objects through
new
method, and will never be trigger if through an association.Could you help me? Thanks in advance.
The text was updated successfully, but these errors were encountered: