[11.x] middleware support for specific method in resource routes

[MrPunyapal]

Enhancement: Middleware Assignment for Resource & Singleton Routes

This pull request enables assigning middleware to specific resourceful methods on resource and singleton routes within the Laravel framework. Key changes include new method 'middlewareFor` for method-specific middleware assignment and updates to resource registration logic to support these configurations.

Motivation: While most developers prefer using routes for defining middleware, this particular case necessitates defining it at the controller level. Alternatively, we could extract all routes into separate routes. Addressing this challenge will streamline our approach.

Examples after merging:

Route::resource('users', UserController::class)->middlewareFor('show', 'auth');
Route::apiResource('users', UserController::class)->middlewareFor(['show', 'update'], 'auth');
Route::resource('users', UserController::class)
    ->middlewareFor('show', 'auth')
    ->middlewareFor('update', 'auth');
Route::apiResource('users', UserController::class)
    ->middlewareFor(['show', 'update'], ['auth', 'verified']);

Route::singleton('users', UserController::class)->middlewareFor('show', 'auth');
Route::apiSingleton('users', UserController::class)->middlewareFor(['show', 'update'], 'auth');
Route::singleton('users', UserController::class)
    ->middlewareFor('show', 'auth')
    ->middlewareFor('update', 'auth');
Route::apiSingleton('users', UserController::class)
    ->middlewareFor(['show', 'update'], ['auth', 'verified']);

I'm up for withoutMiddlewareFor if it's in demand. added withoutMiddlewareFor.

Route::middleware('auth', 'verified', 'other')->group(function () {
    Route::resource('users', UsersController::class)->withoutMiddlewareFor(['create', 'store'], 'verified')
        ->withoutMiddlewareFor('index', ['auth', 'verified'])
        ->withoutMiddlewareFor('destroy', 'other');

    Route::singleton('user', UserController::class)->withoutMiddlewareFor('show', ['auth', 'verified'])
        ->withoutMiddlewareFor(['create', 'store'], 'verified')
        ->withoutMiddlewareFor('destroy', 'other');
});

[aniket-magadum]

Looks good to have 👍

[taylorotwell]

One thing that gives me pause here is the order in which you call middleware and middlewareFor is not respected. The middlewareFor stuff is always put before middleware. What if you don't want that?

[MrPunyapal]

One thing that gives me pause here is the order in which you call middleware and middlewareFor is not respected. The middlewareFor stuff is always put before middleware. What if you don't want that?

Thanks for reviewing and taking an interest in my PR! I'll take a look soon.

[shaedrich]

Route::resource('users', UserController::class)->middlewareFor('show', 'auth');
Route::apiResource('users', UserController::class)->middlewareFor(['show', 'update'], 'auth');
Route::resource('users', UserController::class)
    ->middlewareFor('show', 'auth')
    ->middlewareFor('update', 'auth');
Route::apiResource('users', UserController::class)
    ->middlewareFor(['show', 'update'], ['auth', 'verified']);

Route::singleton('users', UserController::class)->middlewareFor('show', 'auth');
Route::apiSingleton('users', UserController::class)->middlewareFor(['show', 'update'], 'auth');
Route::singleton('users', UserController::class)
    ->middlewareFor('show', 'auth')
    ->middlewareFor('update', 'auth');
Route::apiSingleton('users', UserController::class)
    ->middlewareFor(['show', 'update'], ['auth', 'verified']);

Wouldn't it be more intuitive if this was an associative array? This would be consistent with other resource methods:

Route::resource('photos', PhotoController::class)->names([
    'create' => 'photos.build'
]);

[MrPunyapal]

Wouldn't it be more intuitive if this was an associative array? This would be consistent with other resource methods:

Then we cannot achieve same list of Middleware for 2 or more methods 🤔

So if I need 2 Middleware for show and index then we need to repeat them.

[shaedrich]

That is true, but would there be much harm in that compared to intuitive notation? Also, the idea of using Route::resource() instead of multiple Route::(get|post|put|patch|delete) calls is that all the routes share a significant similarity, but if we start to customized each route anyway, the benefit dwindles.

[MrPunyapal]

One thing that gives me pause here is the order in which you call middleware and middlewareFor is not respected. The middlewareFor stuff is always put before middleware. What if you don't want that?

@taylorotwell, I apologize for the delay. I've updated the code to respect the order and revised the tests accordingly.