7 Laravel Best Practices Worth Knowing
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>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!
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
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
PHP and Python: Comparing Two Popular Programming Languages
Apr 14, 2025 am 12:13 AM
PHP and Python each have their own advantages, and choose according to project requirements. 1.PHP is suitable for web development, especially for rapid development and maintenance of websites. 2. Python is suitable for data science, machine learning and artificial intelligence, with concise syntax and suitable for beginners.
PHP's Current Status: A Look at Web Development Trends
Apr 13, 2025 am 12:20 AM
PHP remains important in modern web development, especially in content management and e-commerce platforms. 1) PHP has a rich ecosystem and strong framework support, such as Laravel and Symfony. 2) Performance optimization can be achieved through OPcache and Nginx. 3) PHP8.0 introduces JIT compiler to improve performance. 4) Cloud-native applications are deployed through Docker and Kubernetes to improve flexibility and scalability.
PHP vs. Other Languages: A Comparison
Apr 13, 2025 am 12:19 AM
PHP is suitable for web development, especially in rapid development and processing dynamic content, but is not good at data science and enterprise-level applications. Compared with Python, PHP has more advantages in web development, but is not as good as Python in the field of data science; compared with Java, PHP performs worse in enterprise-level applications, but is more flexible in web development; compared with JavaScript, PHP is more concise in back-end development, but is not as good as JavaScript in front-end development.
The Enduring Relevance of PHP: Is It Still Alive?
Apr 14, 2025 am 12:12 AM
PHP is still dynamic and still occupies an important position in the field of modern programming. 1) PHP's simplicity and powerful community support make it widely used in web development; 2) Its flexibility and stability make it outstanding in handling web forms, database operations and file processing; 3) PHP is constantly evolving and optimizing, suitable for beginners and experienced developers.
PHP's Purpose: Building Dynamic Websites
Apr 15, 2025 am 12:18 AM
PHP is used to build dynamic websites, and its core functions include: 1. Generate dynamic content and generate web pages in real time by connecting with the database; 2. Process user interaction and form submissions, verify inputs and respond to operations; 3. Manage sessions and user authentication to provide a personalized experience; 4. Optimize performance and follow best practices to improve website efficiency and security.
PHP vs. Python: Core Features and Functionality
Apr 13, 2025 am 12:16 AM
PHP and Python each have their own advantages and are suitable for different scenarios. 1.PHP is suitable for web development and provides built-in web servers and rich function libraries. 2. Python is suitable for data science and machine learning, with concise syntax and a powerful standard library. When choosing, it should be decided based on project requirements.
PHP in Action: Real-World Examples and Applications
Apr 14, 2025 am 12:19 AM
PHP is widely used in e-commerce, content management systems and API development. 1) E-commerce: used for shopping cart function and payment processing. 2) Content management system: used for dynamic content generation and user management. 3) API development: used for RESTful API development and API security. Through performance optimization and best practices, the efficiency and maintainability of PHP applications are improved.
PHP and Python: Code Examples and Comparison
Apr 15, 2025 am 12:07 AM
PHP and Python have their own advantages and disadvantages, and the choice depends on project needs and personal preferences. 1.PHP is suitable for rapid development and maintenance of large-scale web applications. 2. Python dominates the field of data science and machine learning.
