[Feature] Extend stub customization support to "make:factory" and "make:seeder" Artisan commands

[cswaqaas]

Problem

Laravel supports stub customization for many Artisan commands (make:model, make:controller, etc.), but does not currently support it for:

• php artisan make:factory
• php artisan make:seeder

This makes it difficult to enforce standardized boilerplate (like traits or structure) across teams or company projects. Developers are forced to either:

• Manually edit every file after generation
• Write and maintain custom Artisan commands
• Accept inconsistent patterns in large codebases

---

Proposed Solution

Add support for a --stub option in:

• make:factory
• make:seeder

Example usage:

bash

php artisan make:factory ProductFactory --stub=custom
php artisan make:seeder UserSeeder --stub=with_relationships

Behavior:

• Laravel will check for:
• stubs/factory.custom.stub
• stubs/seeder.with_relationships.stub
• If not found, it will fall back to the default stub.

Code Change Overview

1. Update Command Signatures

php

// FactoryMakeCommand.php
protected $signature = 'make:factory {name} {--model=} {--stub=}';

// SeederMakeCommand.php
protected $signature = 'make:seeder {name} {--stub=}';

2. Update buildClass() Method

php

protected function buildClass($name)
{
    $stubName = $this->option('stub') ? "factory.{$this->option('stub')}.stub" : 'factory.stub';
    $stubPath = $this->resolveStubPath("/stubs/{$stubName}");

    if (!file_exists($stubPath)) {
        $stubPath = __DIR__ . '/stubs/factory.stub'; // fallback
    }

    return $this->files->get($stubPath);
}

Similar logic can be added to SeederMakeCommand.

Benefits:

Use case and benefit

Company-wide conventions: Apply traits, comments, or rules uniformly
Advanced seeding: Pre-fill relationship logic
Team collaboration: Avoid manual edits or workarounds
Package development: Publish opinionated stubs

Willingness to Contribute

✅ I’m happy to create a PR if this feature is approved by the Laravel core team.