-
Notifications
You must be signed in to change notification settings - Fork 95
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
Throw out callbacks... #163
Comments
Useful to build associated model instances after guards have run but before the owner model is saved. |
Thanks for the feedback - I'll take that into account, promised. |
never used For example if an instance is versioned with papertrail, you can override the version name doing something like that : def event_fired(current_state, new_state, event)
self.paper_trail_event = event.name
end ... leading to have versions named : 'create', 'activate', 'unactivate', (instead of 'create', 'update', 'update') Generally speaking i think i would keep callbacks :-) |
Sorry, just noticed this is 3 year old issue. |
@duskhacker yep ;) |
....because we have way to many. The goal would be to make
transitions
lean again.The following callbacks:
should go away.
The text was updated successfully, but these errors were encountered: