HairTrigger::migrations_current? returning a wrong result

[elhoyos]

1. Make one of your models to have a simple trigger
2. Generate the migration and run it

HairTrigger::migrations_current? will return false despite you have done step 2.

I can see the migration name from prepared_actions is not present in the trigger definitions. Reason of this is that the method in charge of its initialization, #prepared_name, is never called.

Current tests pass because #generate_migration will iterate through trigger definitions while calling the name-initialization method.

[jenseng]

@elhoyos good catch... in fact it looks like it's only broken if you have a single migration with a single trigger. As soon as you have multiple triggers or trigger migrations, it works correctly (e.g. here's an example where it has correctly and consistently reported out-of-date triggers, but this app has lots of triggers/migrations).

#prepared_name does get called, but only once something is in all_builders (i.e. > 1 trigger). Should be a pretty easy fix.