[8.x] Add method to MigrationsStarted/MigrationEnded events #40334
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
MigrationStarted
andMigrationEnded
events that are fired for individual migrations have amethod
property that can have the valuesup
ordown
to indicate whether this is a migration or a rollback.However, the
MigrationsStarted
andMigrationsEnded
(plural) which run at the beginning and end of a set of migrations do not have this property.This PR adds the
method
property to those events as well.The intended use-case of this change is to allow pre- and post-migration code to run better. For example, consider this code:
There are two problems with the above code when running
migrate:rollback
:project:ensure-extensions
because the database tables already exist so the requirements were clearly met.project:ensure-db
will crash because it is trying to write to database tables that no longer exist.With this PR, the code above can be modified like this: