Empty migration class should not be generated

[ravage84]

It happens that I generate the schema migration and since there is no change in the db (for whatever reason), it generates me an empty skeleton migration class file.

This situation should be caught and either:
a) no schema migrations class should be generated
or
b) the user should be asked what to do.

May be there is a use case for an empty migration class, but I haven't come accross it.

[deizel]

Nice idea - this should be solved now for both a) and b) because the shell already asks this question:

Do you want compare the schema.php file to the database? (y/n)

Answering no will get you a blank template (if needed), and yes will compare and exit if nothing to do.

[ravage84]

🆒 stuff!