migrate:create command seems to create bad migrations when enums are present

[mrispoli24]

I seem to run into issues using the migrate:create command whenever I add new collections or modify an existing one that has an enum value in it. The migration fails to run but then if I remove the previously created enums from the generated migration everything works fine. This happens any time I change an enum value and it's been hard to figure out exactly why. Anyone else run into this issue when working with migrations?