Pest architecture test : Form Request in Livewire

[ahosker]

The Pest architecture test (arch()->preset()->laravel()) enforces that Form Request classes should only be used in Controllers. However, CpdSave.php is importing CpdRequest to reuse its validation rules:

CpdSave.php is a livewire full page controller, am I doing something bad/wrong here? Or should Pest architecture test be adjusted to allow Form Requests to be used in Livewire?

I was able to resolve it by setting arch()->preset()->laravel()->ignoring('App\Livewire'); as a workarround.

[Junaid-PK]

The preset is flagging an HTTP-layer dependency, not saying that Livewire cannot validate the same data.

In the current Laravel preset, the relevant rule is:

expect('App\Http')
    ->toOnlyBeUsedIn(['App\Http', 'App\Providers']);

See Laravel.php. Because CpdRequest lives under App\Http\Requests, importing it from App\Livewire makes the Livewire layer depend on the HTTP layer. A FormRequest also represents an HTTP request boundary, so reusing the class merely to obtain rules couples two delivery mechanisms that do not otherwise need each other.

Keep the preset and extract only the reusable definition:

final class CpdRules
{
    public static function rules(): array
    {
        return [
            // shared rules...
        ];
    }
}

final class CpdRequest extends FormRequest
{
    public function rules(): array
    {
        return CpdRules::rules();
    }
}

final class CpdSave extends Component
{
    protected function rules(): array
    {
        return CpdRules::rules();
    }
}

Put CpdRules somewhere outside App\Http and App\Livewire, such as an application/domain validation namespace. If authorization or normalization is also shared, move that behavior into an application service/value object and let both adapters call it; do not instantiate a FormRequest from Livewire.

Your ignoring('App\Livewire') workaround is valid only if this cross-layer dependency is a deliberate project convention, but it suppresses the preset for every Livewire class. Extracting the rules preserves the architectural check and is the cleaner default.

If this resolves the architecture question, please mark it as the answer so the reason for the preset failure is easy to find.