Reverse doesn't reverse order of operations

[halfmatthalfcat]

It looks like reverse does reverse the individual commands, but if you chain a migration (.create.addForeignKey().addIndex()) and then reverse, it runs the Actions in the same order, causing the migration to fail (since the table will be dropped and then keys/indexes to try to be subsequently dropped).

Is there anyway to change the behavior to match an actual reversal?

[nafg]

Hmm, I guess there should be a .reverse on https://github.com/nafg/slick-migration-api/blob/master/src/main/scala/slick/migration/api/TableMigration.scala#L66

Can you send a PR with tests?