Fix destroy arity

[paneq]

Don't assume that the arity of active record method was not changed. Someone could extend the method so it takes some options and provides defaults.

For example: I extended destroy to work with validations and have a definition
like def destroy(options = {}).

[jeremy]

Looks good. Needs a failing test. Thanks!

[paneq]

Ok, I will provide a test.

[joshk]

Hey paneq,

I tried to create a failing test case for this issue but I could not replicate the case.

Here is the abstract of my test.

From my understanding you are overriding the destroy method in your class, doing some custom checks/logic, and then calling super so the original destroy runs? Please correct me if I am misunderstanding something.

Thanks,

Josh

[dhh]

Please reopen if a test emerges.

[paneq]

I will. I am on holiday right now so I finally have time to deal with it.