Seeder Generation

Purpose and Scope

This document covers the seeder generation system provided by the make:seeder command. Seeders are classes used to populate database tables with test or default data. The document explains the SeederCommand generator, the seeder class structure, file output paths, and how seeders integrate with factory classes to create model instances.

For information about model and factory generation, see Model and Factory Generation. For broader context on the model system generators, see Model System Generators.

Sources: src/Generator/SeederCommand.php1-50

---

Command Overview

The make:seeder command generates seeder classes that extend Hypervel\Database\Seeder. The command is implemented by the SeederCommand class, which follows the standard generator pattern by extending Hyperf\Devtool\Generator\GeneratorCommand.

SeederCommand Class Structure

Sources: src/Generator/SeederCommand.php9-50

Command Signature

Property	Value
Command Name	make:seeder
Description	Create a new seeder class
Arguments	Class name (e.g., UserSeeder)
Base Class	Hyperf\Devtool\Generator\GeneratorCommand

Sources: src/Generator/SeederCommand.php13-20

---

Seeder Class Structure

The generated seeder class follows a simple, consistent structure defined in the seeder.stub template.

Template Structure

Generated Seeder Example

When you run php bin/hypervel.php make:seeder UserSeeder, the following file is created:

Element	Value
Namespace	Database\Seeders
Base Class	Hypervel\Database\Seeder
Method	run(): void
Location	database/seeders/UserSeeder.php

The generated class structure from src/Generator/stubs/seeder.stub1-19:

<?php

declare(strict_types=1);

namespace Database\Seeders;

use Hypervel\Database\Seeder;

class %CLASS% extends Seeder
{
 /**
 * Run the database seeds.
 */
 public function run(): void
 {
 //
 }
}

The %CLASS% placeholder is replaced with the provided class name.

Sources: src/Generator/stubs/seeder.stub1-19

---

File Generation Process

The SeederCommand class overrides key methods to customize the generation behavior for seeder classes.

File Path Resolution

Key Method Behaviors

Method	Behavior	Implementation
getStub()	Returns stub file path	Reads from config or uses default stub at __DIR__ . '/stubs/seeder.stub'
qualifyClass()	Returns class name unchanged	Simply returns the input $name without namespace manipulation
getPath()	Constructs file system path	Uses database/seeders directory by default, configurable via path key
getDefaultNamespace()	Returns empty string	Seeders don't use traditional namespacing pattern

Sources: src/Generator/SeederCommand.php23-49

Configuration Options

The SeederCommand supports configuration through the standard generator config system:

Sources: src/Generator/SeederCommand.php25-41

---

Integration with Factories

Seeders commonly use factory classes to generate model instances. This integration allows for realistic test data generation.

Seeder-Factory Integration Pattern

Typical Usage Pattern

A seeder typically calls factory methods within its run() method:

Factory Definition Reference

The factory stub structure from src/Generator/stubs/factory.stub1-27 shows the corresponding factory class:

Element	Purpose
extends Factory	Provides factory functionality
definition() method	Returns default attribute array
%MODEL_NAMESPACE%	References the model class
@extends Factory<%MODEL%>	Type hint for IDE support

Sources: src/Generator/stubs/factory.stub1-27 src/Generator/stubs/seeder.stub1-19

---

Class Qualification and Namespacing

Unlike most generator commands, SeederCommand uses a simplified qualification strategy.

Namespace Resolution Diagram

The qualifyClass() method at src/Generator/SeederCommand.php31-34 simply returns the input name unchanged:

The namespace Database\Seeders is hardcoded in the stub template at src/Generator/stubs/seeder.stub5

Sources: src/Generator/SeederCommand.php31-34 src/Generator/stubs/seeder.stub5

---

File System Output

The getPath() method constructs the complete file system path for the generated seeder.

Path Construction Flow

The implementation at src/Generator/SeederCommand.php39-44:

Output Location Table

Component	Default Value	Configurable
Base directory	BASE_PATH	No (constant)
Seeder directory	database/seeders	Yes (via path config)
File extension	.php	No
Namespace	Database\Seeders	No (hardcoded in stub)

Sources: src/Generator/SeederCommand.php39-44

---

Stub Template System

The seeder stub template uses a minimal placeholder replacement system.

Stub Placeholder Mapping

Stub Location Resolution

The getStub() method at src/Generator/SeederCommand.php23-26 determines which stub file to use:

Priority	Source	Path
1 (Highest)	Configuration stub key	Custom path specified in config
2 (Default)	Package default	src/Generator/stubs/seeder.stub

Sources: src/Generator/SeederCommand.php23-26 src/Generator/stubs/seeder.stub1-19

---

Command Registration

The SeederCommand is registered through the ConfigProvider along with other generator commands.

Registration Context

The command is registered alongside other model system generators documented in Model System Generators. When a model is generated with the --all flag via ModelCommand, the seeder can be automatically generated (see Model and Factory Generation).

Sources: src/Generator/SeederCommand.php1-50