Confer silent status to nested seeders #2389
Merged
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.
Description
Seeds can call other seeds (https://codeigniter4.github.io/userguide/dbmgmt/seeds.html#nesting-seeders) but since seeds are extensions of the seeder themselves the new seeds will start with their own
silent
value. This means any tests using nesting seeders will start displaying seed results for every test call, very undesirable.This PR has the parent seeder pass its
silent
value to the child before running it.Checklist: