-
Notifications
You must be signed in to change notification settings - Fork 629
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
let whiny_persistence: true be the default now #378
base: master
Are you sure you want to change the base?
Conversation
I'm confused, the changelog says for v3.0.0:
Which seems to not be the case, since this PR is open? |
@andyw8 |
@alto any reason why 5.0 was released without this? Also, I'm curious why the bump to 5.x if it seems like there weren't breaking changes... |
@swrobel We bumped to 5.x because of internal architecture change in AASM |
Is there a way to set it by default on app load/init stage with the current version? |
As many before we have been bitten by the default behaviour of bang events to NOT raise exceptions. It took me quite a while to figure out why this does not work as expected as first search results only returned eferences which state that raising an exception has been "fixed" (for instance aasm#262). Only after quite a while I found out, that raising exceptions on bang events by default will only be part of aasm version 6 (aasm#378). I hope the small documentation change will help others.
👍🏻 should be by default |
@anilmaurya is there any reason this shouldn't be merged? |
Based on #366, this PR sets the default
whiny_persistence
setting to true (DSL/behavior change). So, by default,transition!
will fail if the object is invalid.true