如何在URL不含ID时使用UserController@edit方法映射/user/settings路由

Absolutely! You can absolutely use the same edit() method in your UserController without including an ID in the domain.com/user/settings URL—here's how to pull it off, since this route is almost certainly meant for the currently authenticated user:

1. Define the clean route #

First, set up your route without the ID parameter, and make sure it's protected by the auth middleware (to ensure only logged-in users can access it):

// routes/web.php
use App\Http\Controllers\UserController;

Route::get('/user/settings', [UserController::class, 'edit'])->middleware('auth');

2. Adjust the edit() method to use the authenticated user #

You have two solid options here, depending on whether you want to keep the original method signature or simplify it:

Option A: Simplify the method (most straightforward)

If this route is only for the current user, you can skip the ID parameter entirely and fetch the user directly via the authentication system:

// app/Http/Controllers/UserController.php
use Illuminate\Support\Facades\Auth;
use Illuminate\View\View;

public function edit(): View
{
    // Get the currently logged-in user
    $user = Auth::user();

    // Pass the user to your settings view
    return view('user.settings', compact('user'));
}

Option B: Keep the original method signature (for code reuse)

If you want to reuse the existing edit(User $user) method (that expects a User model instance), you can manually inject the authenticated user when calling the method. One clean way to do this is with a route closure:

// routes/web.php
use App\Http\Controllers\UserController;
use Illuminate\Support\Facades\Auth;

Route::get('/user/settings', function () {
    return app(UserController::class)->edit(Auth::user());
})->middleware('auth');

This way, you don't have to modify your original edit() method at all—it will receive the current user as its parameter, just like it would if the ID was in the URL.

Key Notes #

• The auth middleware is critical here: it ensures only logged-in users can access the settings page, so you'll never have to handle cases where Auth::user() returns null (as long as your middleware is set up correctly).
• This approach keeps your URL clean and user-friendly, which is exactly what you're aiming for with domain.com/user/settings.

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