Detailed explanation of Contracts and Facades in Laravel
Contracts
Contracts actually advocates interface-oriented programming to achieve the purpose of decoupling. These common interfaces have been designed for you by Laravel. These are Contracts.
So how does Laravel know which implementation we need to use?
In Laravel's default Contracts binding, there is such a definition in 'Illuminate/Foundation/Application.php': This is the binding of the default interface implementation.
Recommendation: "laravel tutorial》
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 |
|
When implementing our custom interface, we can use it in ServiceProvider for binding:
1 |
|
Facades
Facades provide a "static" interface for classes available in the application's service container. Laravel "facades" act as "static proxies" for base classes within the service container. Difficult to understand?
We open config/app.php in the project directory and find
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 |
|
Did you find anything? Yes, Facades are actually aliases for a series of classes defined in config/app.php. But these classes all have a common feature, which is to inherit the base Illuminate\Support\Facades\Facade class and implement a method: getFacadeAccessor returns the name.
Customized Facade
Reference http://www.tutorialspoint.com/laravel/laravel_facades.htm
Step 1 −Create a ServiceProvider named TestFacadesServiceProvider, use the following command:
php artisan make:provider TestFacadesServiceProvider
Step 2 − Create an underlying proxy class and name it Create a Facade class called “TestFacades.php” for “TestFacades.php” at “App/Test”. php” at “App/Test/Facades”.
App/Test/Facades/TestFacades.php
1 2 3 4 5 6 7 8 |
|
Step 4 −Create a ServiceProviders class named “ TestFacadesServiceProviders.php” at “App/Test/Facades”.
App/Providers/TestFacadesServiceProviders.php
1 2 3 4 5 6 |
|
Step 5 − Register ServiceProvider in config/app.php Class
Step 6− Register the custom Facade alias in config/app.phpUse test:
Add the following lines in app/ Http/routes.php.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 |
|
− Visit the following URL to test the Facade.
http://localhost:8000/facadeex to view the output
The above is the detailed content of Detailed explanation of Contracts and Facades in Laravel. 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

AI Hentai Generator
Generate AI Hentai for free.

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 Flutter are popular technologies for mobile development. Flutter excels in cross-platform capabilities, performance and user interface, and is suitable for applications that require high performance, cross-platform and customized UI. PHP is suitable for server-side applications with lower performance and not cross-platform.

Database operations in PHP are simplified using ORM, which maps objects into relational databases. EloquentORM in Laravel allows you to interact with the database using object-oriented syntax. You can use ORM by defining model classes, using Eloquent methods, or building a blog system in practice.

Laravel - Artisan Commands - Laravel 5.7 comes with new way of treating and testing new commands. It includes a new feature of testing artisan commands and the demonstration is mentioned below ?

PHP unit testing tool analysis: PHPUnit: suitable for large projects, provides comprehensive functionality and is easy to install, but may be verbose and slow. PHPUnitWrapper: suitable for small projects, easy to use, optimized for Lumen/Laravel, but has limited functionality, does not provide code coverage analysis, and has limited community support.

The latest versions of Laravel 9 and CodeIgniter 4 provide updated features and improvements. Laravel9 adopts MVC architecture and provides functions such as database migration, authentication and template engine. CodeIgniter4 uses HMVC architecture to provide routing, ORM and caching. In terms of performance, Laravel9's service provider-based design pattern and CodeIgniter4's lightweight framework give it excellent performance. In practical applications, Laravel9 is suitable for complex projects that require flexibility and powerful functions, while CodeIgniter4 is suitable for rapid development and small applications.

Compare the data processing capabilities of Laravel and CodeIgniter: ORM: Laravel uses EloquentORM, which provides class-object relational mapping, while CodeIgniter uses ActiveRecord to represent the database model as a subclass of PHP classes. Query builder: Laravel has a flexible chained query API, while CodeIgniter’s query builder is simpler and array-based. Data validation: Laravel provides a Validator class that supports custom validation rules, while CodeIgniter has less built-in validation functions and requires manual coding of custom rules. Practical case: User registration example shows Lar

PHP Unit and Integration Testing Guide Unit Testing: Focus on a single unit of code or function and use PHPUnit to create test case classes for verification. Integration testing: Pay attention to how multiple code units work together, and use PHPUnit's setUp() and tearDown() methods to set up and clean up the test environment. Practical case: Use PHPUnit to perform unit and integration testing in Laravel applications, including creating databases, starting servers, and writing test code.

When choosing a framework for large projects, Laravel and CodeIgniter each have their own advantages. Laravel is designed for enterprise-level applications, offering modular design, dependency injection, and a powerful feature set. CodeIgniter is a lightweight framework more suitable for small to medium-sized projects, emphasizing speed and ease of use. For large projects with complex requirements and a large number of users, Laravel's power and scalability are more suitable. For simple projects or situations with limited resources, CodeIgniter's lightweight and rapid development capabilities are more ideal.
