Resource routes for soft-deleted models (softResource & softApiResource)

[SaadMajeed565]

Currently, we have Route::resource() and Route::apiResource() which save time and help keep web.php or api.php clean.

I propose adding two new helper functions: softResource() and softApiResource(). These would automatically generate routes for soft-deleted models, including:

• trashed() – to list all soft-deleted records
• restore($id) – to restore a soft-deleted model
• forceDelete($id) – to permanently delete a model

This would eliminate the need to define these routes manually. Often developers add these routes under show() or other routes, which can break RESTful URL conventions.

Having built-in support for soft-delete resource routes would make working with soft-deleted models more consistent and cleaner.

[marius-ciclistu]

Wouldn't this just duplicate the same routes without the softDeleted scope? You can do this even now using a diferent scope.

[SaadMajeed565]

That’s true — it can be done today.

However, the recommendation is about first-class support to keep route and API files clean and intentional, so developers don’t need to manually define separate routes for common soft-delete actions.
This becomes especially relevant in cases like super-admin–only access to trashed resources. When a controller already uses Route::resource(), developers are forced to add extra custom routes just to handle trashed, restore, or forceDelete, which breaks the otherwise clean and consistent resource structure.

While similar behavior could be achieved using query parameters, permission-based actions (such as restoring or permanently deleting records) are clearer, safer, and more expressive when exposed as explicit routes rather than implicit query logic.

A softResource() / softApiResource() helper would formalize these patterns, improve readability, and reduce repetitive boilerplate—similar to how apiResource() improved API routing clarity

[marius-ciclistu]

There is a corner case not handled by laravel to add scopes based on auth user. I fixed that but laravel did not. With that feature you don't have to register twice the routes.

[macropay-solutions]

#51825