The modern, modular and flexible migration tool for any database
MIT License
Published by joakimbeng 9 months ago
Published by joakimbeng 9 months ago
Published by joakimbeng 9 months ago
Published by joakimbeng 9 months ago
Published by joakimbeng 9 months ago
Published by joakimbeng 9 months ago
Published by joakimbeng 9 months ago
Published by joakimbeng 9 months ago
Published by joakimbeng 9 months ago
onMigrationRemoveStart
, onMigrationRemoveSuccess
and onMigrationRemoveError
the onMigrationStart
, onMigrationSuccess
and onMigrationError
methods should be used and the reporter can still format the output differently depending on the current command (which it receives in the onInit
method). This is a BREAKING CHANGE.Published by joakimbeng 9 months ago
Published by joakimbeng 9 months ago
Published by joakimbeng 9 months ago
Published by joakimbeng 9 months ago
Published by joakimbeng 9 months ago
Published by joakimbeng 9 months ago
--from
or --to
CLI options are used the given migration name (or path to migration file) must exist. This is a BREAKING CHANGE from before. The reasoning is that by forcing the migrations to exist you avoid accidentally running migrations you don't intend to, because a simple typo could have the effect that many unwanted migrations is executed so it's better to show an error if that's the case.onMigrationStart
, onMigrationSuccess
and onMigrationError
reporter methods when reporting the command progress. It's also in preparation for adding --from
and --to
CLI options for the "remove" command, similar to how the same options work for the "up" command.--from
and --to
CLI options. This is very useful from terminals that support autocomplete for file paths. It also makes it possible to copy the path to a migration file from Emigrate's output and use that as either --from
and --to
directly.Published by joakimbeng 9 months ago
Published by joakimbeng 9 months ago
Published by joakimbeng 9 months ago
Published by joakimbeng 9 months ago
Published by joakimbeng 9 months ago