In rails 5.2, calling destroy twice on a paranoid record would run the after_commit on: :destroy method twice. We discovered when upgrading to rails 6 that this is no longer the case. Not sure if this is an issue but the expected behavior around those callbacks should be documented. The after_destroy callbacks however do run correctly.
In rails 5.2, calling
destroy
twice on a paranoid record would run theafter_commit on: :destroy
method twice. We discovered when upgrading to rails 6 that this is no longer the case. Not sure if this is an issue but the expected behavior around those callbacks should be documented. Theafter_destroy
callbacks however do run correctly.