leap_web.git/help/app/models/account_extension, branch 0.5.2 [leap_web] move engines into engines directory 2014-04-11T08:07:23+00:00 Azul azul@leap.se 2014-04-11T08:03:19+00:00 636692f9921bd695d726695d2d46c91f5a6e56f3 Also renamed help to support so it's harder to confuse it with documentation 
Also renamed help to support so it's harder to confuse it with documentation
destroy all tickets created by a user when account is destroyed 2013-11-06T10:30:33+00:00 Azul azul@leap.se 2013-11-06T10:26:46+00:00 24598b5c5e4df20c423ec74ea8e9df1592483c6b In order to keep the users engine independent of the tickets engine i added a generic load hook to the account model. The tickets engine then monkeypatches the account destruction and destroys all tickets before the user is destroyed. The tickets are destroyed first so that even if things break there should never be tickets with an outdated user id. I would have prefered to use super over using an alias_method_chain but I have not been able to figure out a way to make account a superclass of the account extension and still refer to Account from the users engine. 
In order to keep the users engine independent of the tickets engine i added a generic load hook to the account model. The tickets engine then monkeypatches the account destruction and destroys all tickets before the user is destroyed.

The tickets are destroyed first so that even if things break there should never be tickets with an outdated user id.

I would have prefered to use super over using an alias_method_chain but I have not been able to figure out a way to make account a superclass of the account extension and still refer to Account from the users engine.