Using slug instead of id in Laravel for routing model binding can be achieved by overriding the getRouteKeyName method. First, override the getRouteKeyName method in the model to return 'slug'; second, it is recommended to add a unique index to the slug field to ensure accuracy and check the uniqueness of the existing data; finally, keep the route and controller code unchanged, Laravel will automatically parse the model through slug. In addition, pay attention to issues such as clearing routing cache, handling soft deletion situations, and field naming consistency.
In Laravel, routing model binding uses the model's primary key (usually id
) by default. But many times we want to use more friendly identifiers, such as slug
, for binding. This is actually not complicated, it only takes a few steps to achieve it.

Modify the getRouteKeyName
method in the model
Laravel provides an easy way to customize the fields used by model binding. You just need to override the getRouteKeyName
method in the corresponding model and return the field name you want to use, such as slug
.
For example, in the Post
model:

public function getRouteKeyName() { return 'slug'; }
In this way, when you use {post}
in your route, Laravel will automatically find the corresponding model instance based on the slug
field.
Ensure that the database field exists and has unique constraints (optional)
Although it is not a mandatory requirement, in order to ensure the accuracy of route matching, it is recommended to add a unique index to the slug
field. You can add unique indexes by migrating files:

Schema::table('posts', function (Blueprint $table) { $table->string('slug')->unique()->change(); });
This can prevent multiple records from having the same slug, resulting in inaccurate model binding results.
Note: If you already have some data, make sure that
slug
of the existing data is unique before performing this operation, otherwise an error will be reported.
Routing and controller stay the same
After setting up the model, no modifications are required to your route and controller code. For example:
Route::get('/posts/{post}', [PostController::class, 'show']);
In the controller:
public function show(Post $post) { return view('post.show', compact('post')); }
Laravel will automatically parse Post
model through slug
instead of using id
.
Frequently Asked Questions and Precautions
- Caching issues : If you have tested routing before, you may need to clear the routing cache: run
php artisan route:clear
. - Soft Deletion Processing : If the model uses soft deletion, by default, the model binding will not consider records that have been soft deleted. If you want to change this behavior, you need to customize the binding logic.
- Field naming consistency : Ensure that the field names returned by the model method are exactly consistent with the database fields, including case and underscore styles.
Basically that's it. Just change one method and you can easily use slug
instead of id
to bind the model, which is both friendly and practical.
The above is the detailed content of How to customize the key for route model binding to use a slug?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

There are three ways to add custom validation rules in Laravel: using closures, Rule classes, and form requests. 1. Use closures to be suitable for lightweight verification, such as preventing the user name "admin"; 2. Create Rule classes (such as ValidUsernameRule) to make complex logic clearer and maintainable; 3. Integrate multiple rules in form requests and centrally manage verification logic. At the same time, you can set prompts through custom messages methods or incoming error message arrays to improve flexibility and maintainability.

The core methods for Laravel applications to implement multilingual support include: setting language files, dynamic language switching, translation URL routing, and managing translation keys in Blade templates. First, organize the strings of each language in the corresponding folders (such as en, es, fr) in the /resources/lang directory, and define the translation content by returning the associative array; 2. Translate the key value through the \_\_() helper function call, and use App::setLocale() to combine session or routing parameters to realize language switching; 3. For translation URLs, paths can be defined for different languages ??through prefixed routing groups, or route alias in language files dynamically mapped; 4. Keep the translation keys concise and

ToworkeffectivelywithpivottablesinLaravel,firstaccesspivotdatausingwithPivot()orwithTimestamps(),thenupdateentrieswithupdateExistingPivot(),managerelationshipsviadetach()andsync(),andusecustompivotmodelswhenneeded.1.UsewithPivot()toincludespecificcol

Laravelprovidesacleanandflexiblewaytosendnotificationsviamultiplechannelslikeemail,SMS,in-appalerts,andpushnotifications.Youdefinenotificationchannelsinthevia()methodofanotificationclass,andimplementspecificmethodsliketoMail(),toDatabase(),ortoVonage

ServiceProvider is the core mechanism used in the Laravel framework for registering services and initializing logic. You can create a custom ServiceProvider through the Artisan command; 1. The register method is used to bind services, register singletons, set aliases, etc., and other services that have not yet been loaded cannot be called; 2. The boot method runs after all services are registered and is used to register event listeners, view synthesizers, middleware and other logic that depends on other services; common uses include binding interfaces and implementations, registering Facades, loading configurations, registering command-line instructions and view components; it is recommended to centralize relevant bindings to a ServiceProvider to manage, and pay attention to registration

Dependency injection automatically handles class dependencies through service containers in Laravel without manual new objects. Its core is constructor injection and method injection, such as automatically passing in the Request instance in the controller. Laravel parses dependencies through type prompts and recursively creates the required objects. The binding interface and implementation can be used by the service provider to use the bind method, or singleton to bind a singleton. When using it, you need to ensure type prompts, avoid constructor complications, use context bindings with caution, and understand automatic parsing rules. Mastering these can improve code flexibility and maintenance.

Laravel performance optimization can improve application efficiency through four core directions. 1. Use the cache mechanism to reduce duplicate queries, store infrequently changing data through Cache::remember() and other methods to reduce database access frequency; 2. Optimize database from the model to query statements, avoid N 1 queries, specifying field queries, adding indexes, paging processing and reading and writing separation, and reduce bottlenecks; 3. Use time-consuming operations such as email sending and file exporting to queue asynchronous processing, use Supervisor to manage workers and set up retry mechanisms; 4. Use middleware and service providers reasonably to avoid complex logic and unnecessary initialization code, and delay loading of services to improve startup efficiency.

Methods to manage database state in Laravel tests include using RefreshDatabase, selective seeding of data, careful use of transactions, and manual cleaning if necessary. 1. Use RefreshDatabasetrait to automatically migrate the database structure to ensure that each test is based on a clean database; 2. Use specific seeds to fill the necessary data and generate dynamic data in combination with the model factory; 3. Use DatabaseTransactionstrait to roll back the test changes, but pay attention to its limitations; 4. Manually truncate the table or reseed the database when it cannot be automatically cleaned. These methods are flexibly selected according to the type of test and environment to ensure the reliability and efficiency of the test.
