Laravel Eloquent模型中使用Request或Facade是否合理？

Hey there! As someone who fumbled through Laravel's learning curve not too long ago, I totally get this confusion—let’s break this down clearly and practically.

First, the technical vs. practical answer #

Technically, you can use Facades like Request in Eloquent models—Laravel makes them available across your entire app, so code like Request::input('name') won’t throw an error. But that doesn’t mean you should do it, especially for HTTP-related Facades like Request.

Why using Request (or HTTP-tied Facades) in models is a bad idea #

• Breaks single responsibility: Eloquent models exist to handle data and data-focused business logic—think database queries, relationships, model-specific validation, or rules tied to your data. The Request class belongs to the HTTP layer, whose job is to handle incoming requests, validate user input, and pass clean data to your models/services. Mixing these muddles each component’s purpose.
• Creates fragile coupling: If your model depends on Request, it’s now tied to an HTTP context. Try calling that model method from a CLI command, queue job, or scheduled task—there’s no HTTP request there, so your code will crash.
• Makes testing a headache: Testing model logic becomes way more complex because you’ll have to mock an entire HTTP request context just to test a simple model method. Instead, you could pass the required data directly as parameters and test it easily.
• Hurts readability: Other developers (or future you) looking at the model will expect to find data-related logic, not HTTP request handling. Mixing these concerns makes the code harder to follow and modify later.

The right approach: Pass data explicitly #

Extract what you need from the Request in your controller (or form request class), then pass that clean data to your model. Here’s a quick example:

// In your controller
public function update(Request $request, User $user)
{
    // Validate the request first
    $validated = $request->validate([
        'name' => 'required|string|max:255',
        'email' => 'required|email|unique:users,email,' . $user->id,
    ]);

    // Pass validated data to the model method
    $user->updateProfile($validated);

    return redirect()->route('users.show', $user);
}

// In your User model
public function updateProfile(array $data)
{
    return $this->update([
        'name' => $data['name'],
        'email' => $data['email'],
        // Add any model-specific logic here
    ]);
}

Are any Facades okay to use in models? #

Absolutely! Facades that aren’t tied to the HTTP context are fair game. For example:

• Cache (to cache frequent query results)
• Log (to log model-specific events like failed updates)
• Storage (if your model handles file attachments)
• DB (though you’ll usually prefer Eloquent’s query builder)

These are service-layer tools that don’t depend on an HTTP request, so using them in models doesn’t create unwanted coupling.

Final takeaway #

Facades aren’t restricted to controllers—they’re available app-wide—but use them in line with separation of concerns. HTTP-related Facades like Request have no place in Eloquent models; they’ll make your code fragile and hard to maintain. Stick to passing explicit data to your models instead!

内容的提问来源于stack exchange，提问作者kerby