[5.3] Show seed output prior to running, instead of after #17318
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GrahamCampbell
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently the database seeder shows its output prior to running the seed class. For example:
# runs seed class UserSeeder Seed: UserSeederThis is a simple change that proposes to show the output before running the seeder:
Seeding: UserSeeder # runs seed class UserSeederThis may seem minor, but on a project with long-running seeds it's difficult to know which seed is currently running. It's even more annoying if a seed breaks (for whatever reason), you don't actually know which seed it was (without pulling up the code and looking at the seed order).