Every web developer has his or her own style when writing code. At the same time, if we use the Laravel framework, everything is ready, but often we misuse the terminology here. It's not a big deal when it comes to different styles, but we have to make sure that our code follows good style. This means our code must be extensible, maintainable and testable. [Related recommendations: laravel video tutorial]
What makes our code bad or good? Because PHP is an object-oriented language, we should follow object-oriented principles, such as SOLID design principles, and consider using object-oriented mechanisms, such as inheritance, abstraction, etc. Additionally, Laravel has a large community and sometimes there are some community-created conventions. Therefore, other laravel developers who follow these conventions are able to understand our code better and faster. In this article, I will show you 7 best practices on Laravel based on object-oriented principles and some Laravel community conventions.
1. Fat model, thin controller
If we have a very complex query builder or raw SQL statement, we should move this query to the model or In the warehouse.
Bad:
<?php
public function index()
{
$partners = Partner::where('email_verified_at', '!=', null)
->with(['products' => function ($q) {
$q->whereDate('created_at', now());
}])
->get();
return view('index', ['partners' => $partners]);
}Good:
<?php
public function index()
{
return view('index', ['partners' => $this->partner->newProducts()]);
}
class Partner extends Model
{
public function newProducts()
{
return $this->where('email_verified_at', '!=', null)
->with(['products' => function ($q) {
$q->whereDate('created_at', now());
}])
->get();
}
}2. The business logic in the service class
is the same as the first one above Point related, we should have a thin controller and then we should move all business logic into separate service classes. So the controller should have only one responsibility and hopefully we can reuse this service in other controllers.
Bad:
<?php
public function store(Request $request)
{
$user = User::create();
$user->update(['last_login' => now()]);
dispatch(new UserCreated($user));
// ...
}Good:
<?php
public function store(Request $request)
{
$this->userService->create($request);
....
}
class UserService
{
public function create($request)
{
// ...
}
}3.Eloquent queries are better than native SQL statements.
Using Eloquent for queries is more readable, avoids SQL injection, and is easier to maintain.
Bad:
<?php
SELECT *
FROM `articles`
WHERE EXISTS (SELECT *
FROM `users`
WHERE `articles`.`user_id` = `users`.`id`
AND EXISTS (SELECT *
FROM `profiles`
WHERE `profiles`.`user_id` = `users`.`id`)
AND `users`.`deleted_at` IS NULL)
AND `verified` = '1'
AND `active` = '1'
ORDER BY `created_at` DESCGood:
<?php Article::has('user.profile')->verified()->latest()->get();
4.DRY (Don't Repeat Yourself)
We should Consider moving reusable logic/component parts to separate places.
In the blade template, we can use components to reuse the front-end part. In the server, we can move the logic to a separate service class, Eloquent scope, or even create our own package.
<!DOCTYPE html> <html> <head> <title>DRY</title> </head> <body> <h1 id="Custom-nbsp-Calendar">Custom Calendar</h1> <x-custom-calendar> </body> </html>
5. Do not execute queries in Blade templates
Although it is possible to execute queries in Blade templates, it is best not to do so.
bad. Will cause N 1 problem.
@foreach (User::all() as $user)
{{ $user->email }}
@endforeachOkay:
$users = User::all(); // Server Query
@foreach ($users as $user)
{{ $user->email }}
@endforeach6. Using database transactions
If we have some complex and lengthy logic/queries, then we should consider Use database transactions. By using this feature, we can easily roll back the database if needed to ensure that our data is not saved to the database, so we are confident that our data is reliable.
<?php
public function store(Request $request)
{
DB::beginTransaction();
$user = User::create();
$response = app('service')->create($user);
if (!$response) {
DB::rollback();
return;
}
// ...
DB::commit();
}7. Don’t hardcode text
We should not hardcode any text in code/controller. This makes it easy to maintain and extend in the future. If we want to display a message to the user we can use translations, constants in models/classes to set any value or config files to save our configuration.
trans('user.created'); // 'User Successfully Created' $types = Product::TYPES; // Const in a Class/Model
Original address: https://cerwyn.medium.com/7-best-practices-in-laravel-you-should-know-2ed9878293de
Translation address: https ://learnku.com/laravel/t/67021
For more programming-related knowledge, please visit: programming video! !
The above is the detailed content of 7 Laravel Best Practices Worth Knowing. For more information, please follow other related articles on the PHP Chinese website!
Last Laravel version: Migration TutorialMay 14, 2025 am 12:17 AMWhat new features and best practices does Laravel's migration system offer in the latest version? 1. Added nullableMorphs() for polymorphic relationships. 2. The after() method is introduced to specify the column order. 3. Emphasize handling of foreign key constraints to avoid orphaned records. 4. It is recommended to optimize performance, such as adding indexes appropriately. 5. Advocate the idempotence of migration and the use of descriptive names.
What is the Latest LTS Version of Laravel?May 14, 2025 am 12:14 AMLaravel10,releasedinFebruary2023,isthelatestLTSversion,supportedforthreeyears.ItrequiresPHP8.1 ,enhancesLaravelPennantforfeatureflags,improveserrorhandling,refinesdocumentation,andoptimizesperformance,particularlyinEloquentORM.
Stay Updated: The Newest Features in the Latest Laravel VersionMay 14, 2025 am 12:10 AMLaravel's latest version introduces multiple new features: 1. LaravelPennant is used to manage function flags, allowing new features to be released in stages; 2. LaravelReverb simplifies the implementation of real-time functions, such as real-time comments; 3. LaravelVite accelerates the front-end construction process; 4. The new model factory system enhances the creation of test data; 5. Improves the error handling mechanism and provides more flexible error page customization options.
Implementing Soft Delete in Laravel: A Step-by-Step TutorialMay 14, 2025 am 12:02 AMSoftleteinelelavelisling -Memptry-braceChortsDevetus -TeedeecetovedinglyDeveledTeecetteecedelave
Current Laravel Version: Check the Latest Release and UpdatesMay 14, 2025 am 12:01 AMLaravel10.xisthecurrentversion,offeringnewfeatureslikeenumsupportinEloquentmodelsandimprovedroutemodelbindingwithenums.Theseupdatesenhancecodereadabilityandsecurity,butrequirecarefulplanningandincrementalimplementationforasuccessfulupgrade.
How to Use Laravel Migrations: A Step-by-Step TutorialMay 13, 2025 am 12:15 AMLaravelmigrationsstreamlinedatabasemanagementbyallowingschemachangestobedefinedinPHPcode,whichcanbeversion-controlledandshared.Here'showtousethem:1)Createmigrationclassestodefineoperationslikecreatingormodifyingtables.2)Usethe'phpartisanmigrate'comma
Finding the Latest Laravel Version: A Quick and Easy GuideMay 13, 2025 am 12:13 AMTo find the latest version of Laravel, you can visit the official website laravel.com and click the "Docs" button in the upper right corner, or use the Composer command "composershowlaravel/framework|grepversions". Staying updated can help improve project security and performance, but the impact on existing projects needs to be considered.
Staying Updated with Laravel: Benefits of Using the Latest VersionMay 13, 2025 am 12:08 AMYoushouldupdatetothelatestLaravelversionforperformanceimprovements,enhancedsecurity,newfeatures,bettercommunitysupport,andlong-termmaintenance.1)Performance:Laravel9'sEloquentORMoptimizationsenhanceapplicationspeed.2)Security:Laravel8introducedbetter
Hot AI Tools
Undresser.AI Undress
AI-powered app for creating realistic nude photos
AI Clothes Remover
Online AI tool for removing clothes from photos.
Undress AI Tool
Undress images for free
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
Dreamweaver Mac version
Visual web development tools
SublimeText3 Mac version
God-level code editing software (SublimeText3)
WebStorm Mac version
Useful JavaScript development tools
Atom editor mac version download
The most popular open source editor
DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software
