Refactor BaseCommand to improve module resolution and add support for… #2114
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.
Summary
Currently, when running migrations, modules are loaded in ascending (asc) alphabetical order, which causes issues with database tables' foreign key constraints.
For example, suppose an
Entry
module depends on aTransaction
module, but the Entry module is processed first due to alphabetical ordering. In that case, the migration will fail because the required foreign key (transaction_id) references don't exist yet.Describe in detail what you propose, show (preferable) code examples and also signal if you're willing to work on it!
@dcblogdev