Fix for Running Root Migrations Before Module Migrations #1919
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.
Hi,
While testing the
module:migrate-fresh
command, I discovered that root migrations were not being executed before the module migrations.This issue occurs because, in the Laravel framework's
migrate
command, the default migration paths are merged when the method is called, but they are not registered by default. You can see the relevant code here: Laravel Framework Migration Command.This pull request addresses and fixes this issue, ensuring that root migrations are executed before module migrations.