It would be super convenient to have a mite diff command that would launch a difftool with a dirty migration on disk, and the clean executed migration.
This would obviously require getting access to the last "clean" version of the migration, which there are two potential ways to do:
add the option to store the full migration text in the database.
It would be super convenient to have a
mite diff
command that would launch a difftool with a dirty migration on disk, and the clean executed migration.This would obviously require getting access to the last "clean" version of the migration, which there are two potential ways to do: