We'll respond shortly.
save!, and friends, the
destroy! method didn’t exist in Rails 3.
It took me a while to get used to
destroy instead of
destroy! from the Rails console and from test code, but Rails 4 will provide
destroy!, which is different from
destroy in the following ways:
falseon failure, it will raise
before_destroycallback that returns false, it will still raise
There’s going to be a lot less cycles of “write a test that calls
destroy!, see a
destroy, and re-run the test” once Rails 4 is released. I know I’ve lost a few minutes of my life doing that :)