Why is the response type returned when creating a new default middleware not its own response type?

[ZhangChengLin]

Code involved:

framework/src/Illuminate/Routing/Console/stubs/middleware.stub

Line 14 in eb04fb4

* @param \Closure(\Illuminate\Http\Request): (\Symfony\Component\HttpFoundation\Response) $next

Scenes:

Laravel 11 

php artisan make:middleware SomeMiddleware

First of all, this question is a question from a newbie.

Why continue to use: \Symfony\Component\HttpFoundation\Response now
Shouldn't it be recommended to use Illuminate\Http\Response

Why hasn't it changed yet? Is it to maintain compatibility?
Or what are the benefits of doing so?

Similar questions

[marius-mcp]

namespace Illuminate\Http;

use Symfony\Component\HttpFoundation\Response as SymfonyResponse;

class Response extends SymfonyResponse

[marius-mcp]

from this #50369
Illuminate\Http\RedirectResponse extends Symfony\Component\HttpFoundation\Response
Illuminate\Routing\Redirector does not.

So you question should be why is the dock block not up to date not why it is not returning Illuminate\Http\Response

[ZhangChengLin]

I don't understand what you said either.

I mean, when will he become like this?

* @param \Closure(\Illuminate\Http\Request): (\Illuminate\Http\Response) $next

[marius-mcp]

I can only guess that using Symfony response covers more than \Illuminate\Http\Response does, and as long as Symfony components are used in laravel, it is safer to put the "highest" parent there.

[ZhangChengLin]

I thought Laravel's response class extended SymfonyResponse
Things will be added.

class Response extends SymfonyResponse

[marius-mcp]

This is what I showed you here #51334 (comment)

But even if it is extending it, there is still the possibility for the parent to be returned.