Download the PHP package amdadulhaq/route-resource-paths-laravel without Composer

Route Resource Paths Laravel Package

This Laravel package allows you to define custom paths for create and edit routes in resource controllers. It extends the functionality of Laravel's resource routing by providing macros to set these paths globally or for specific resources.

Features

• Set global custom paths for create and edit actions across all resource routes
• Customize paths individually for each resource route
• Support for both regular resource routes and singleton resource routes
• Works seamlessly with both Route::resource() and Route::resources() methods
• Override global settings with per-resource customization
• Zero configuration required - works out of the box

Installation

You can install the package via composer:

Once installed, the service provider will be registered automatically by Laravel.

Requirements

• PHP 8.2 or higher
• Laravel 11.x, 12.x, or 13.x

Configuration

No additional configuration is required. The package uses Laravel's built-in service container to bind and replace the default resource registrar.

Usage

Setting Global Paths

To set custom paths for the create and edit actions that will apply globally to all resource routes, use the Route::resourcePaths() method:

After setting these global paths, all resource routes defined using Route::resource() will use these custom paths instead of the default ones.

Using Global Paths with Route::resource()

The global paths will automatically be applied to all resource controllers like this:

This will generate routes such as:

• GET /posts/add instead of GET /posts/create
• GET /posts/{post}/change instead of GET /posts/{post}/edit

Using Global Paths with Route::resources()

You can also use the global paths when registering multiple resource controllers at once:

This will apply the same custom paths to both photos and posts resource routes.

Setting Custom Paths for Specific Resources

If you want to set custom paths for a specific resource, you can do so directly when defining the resource using the paths() method:

This will only affect the routes for the users resource:

• GET /users/add instead of GET /users/create
• GET /users/{user}/change instead of GET /users/{user}/edit

Combining Global and Specific Paths

You can set global paths and override them for specific resources:

In this example:

• Posts will use /posts/add and /posts/{post}/change
• Users will use /users/register and /users/{user}/update

Setting Paths for Multiple Resources

When registering multiple resources with Route::resourcesWithPaths(), you can apply custom paths to all of them:

Singleton Resource Paths

The package also supports singleton resources. Use the Route::singletonPaths() method to set global singleton paths:

Then define your singleton resource:

This will generate the following routes:

• GET /profile/setup instead of GET /profile/create
• GET /profile/modify instead of GET /profile/edit

Custom Paths for Specific Singleton Resources

You can also set custom paths per singleton resource:

API Reference

Route Macros

Route::resourcePaths(array $paths)

Sets global custom paths for all resource routes.

Parameters:

• $paths (array): An associative array where keys are action names (create, edit) and values are the custom path strings.

Example:

Route::singletonPaths(array $paths)

Sets global custom paths for all singleton resource routes.

Parameters:

• $paths (array): An associative array where keys are action names (create, edit) and values are the custom path strings.

Example:

Route::resourcesWithPaths(array $resources)

Registers multiple resource controllers at once and returns a chainable object that can apply custom paths.

Parameters:

• $resources (array): An associative array where keys are resource names and values are controller class names.

Returns: An object with a paths() method to apply custom paths.

Example:

Resource Registration Methods

PendingResourceRegistration::paths(array $paths)

Sets custom paths for a specific resource registration.

Parameters:

• $paths (array): An associative array where keys are action names (create, edit) and values are the custom path strings.

Returns: the pending registration, for method chaining. paths() is a macro registered by the package's service provider — no extra setup needed.

Example:

PendingSingletonResourceRegistration::paths(array $paths)

Sets custom paths for a specific singleton resource registration.

Parameters:

• $paths (array): An associative array where keys are action names (create, edit) and values are the custom path strings.

Returns: the pending singleton registration, for method chaining. paths() is a macro registered by the package's service provider — no extra setup needed.

Example:

Complete Example

Here's a complete example showing various ways to use the package:

Troubleshooting

Paths not working

If the custom paths are not working:

1. Ensure the service provider is registered (it should be auto-discovered in Laravel)
2. Check that you're calling Route::resourcePaths()/Route::singletonPaths() before defining your resources
3. Verify the package is installed correctly by checking composer show amdadulhaq/route-resource-paths-laravel

Conflicts with other packages

This package rebinds Illuminate\Routing\ResourceRegistrar to PathsResourceRegistrar and registers a paths() macro on the pending resource registrations. If another package rebinds ResourceRegistrar too, only the last one registered wins. If custom paths stop working after adding a new package, check for a similar router/registrar override by:

1. Checking the order of service provider registration
2. Testing with a fresh Laravel installation
3. Reviewing other packages' documentation

Migration Guide

If you're upgrading from an older version:

1. v2.0.0: Route::resources() was renamed to Route::resourcesWithPaths() — the old name collided with Laravel's own native Router::resources() method, which meant Route::resources([...])->paths([...]) never actually worked in the first place (it silently called Laravel's method instead, which returns void). If you were only using Route::resources([...]) without chaining ->paths() and relying on Route::resourcePaths() for global paths, nothing changes for you.
2. v2.0.0: Laravel 10 support was dropped; the minimum is now Laravel 11.
3. Check the changelog for the full list of changes.
4. Ensure your Laravel version meets the requirements (11.x, 12.x, or 13.x).

Credits

• Amdadul Haq
• All Contributors

License

The MIT License (MIT). Please see License File for more information.

Contributing

If you find any issues or have suggestions for improvements, feel free to create a pull request or open an issue on the GitHub repository.

Support

For support, email [email protected] or open an issue on GitHub.