What is a Blade template?
Blade template is a template engine provided by Laravel. It is simple and powerful. Blade allows the use of native PHP code in views. Laravel uses compiled cache files instead of the view itself, so Blade is very useful for applications. It's zero overhead.
Blade template is:
Blade is a template engine provided by Laravel. It is simple and powerful. Unlike other PHP template engines, Blade allows the use of native PHP code in views.
In fact, all Blade views will eventually be compiled into native PHP code and cached in the storage/framework/views folder.
Laravel uses these compiled cache files, not the views themselves, so Blade has zero overhead for the application. When you modify a view file, it is recompiled and cached for use. Blade views have the suffix name of blade.php and are generally stored in the resources/views folder.
Template inheritance:
1. Define layout file
The main two advantages of Blade template engine are "template inheritance" ” and “Block.” To give a simple example, in a project, almost all pages have the same layout. At this time, this layout can be extracted and used as a master page. All pages that inherit this master page will have the same layout effect. , becoming a child page of the master page. The master page is also called a layout file, and the layout file is a Blade view:
<!-- Stored in resources/views/layouts/app.blade.php -->
<html>
<head>
<title>App Name - @yield('title')</title>
</head>
<body>
@section('sidebar')
This is the master sidebar.
@show
<div class="container">
@yield('content')
</div>
<body>
</html>In addition to the basic HTNL tags, the layout file also uses two instructions: @section and @yield. @section defines the block, and @yield defines the content in the block.
under. to define subpages of the layout file.
2. Inherit the layout file
In the subpage, use Blade's @extends directive to specify the "inherited" layout file, and use the @section directive to specify the "inherited" layout file in the layout file. Inject content where the @section and @yield directives are used:
<!-- Stored in resources/views/child.blade.php -->
@extends('layouts.app')
@section('title','Page Title')
@section('sidebar')
<p> This is appended to the master sideebar</p>
@endsection
@section('content')
<p>This ismy body content. </p>
@endsectionYou can see that where the @yield directive is used in the layout file, @section is still used to inject content in the subpage; in the layout file, use One benefit of the @section directive definition is that when using @section injection in child pages, you can use the @parent directive to append (rather than overwrite) the content in the layout file where the @yield directive is used in the layout file. It can't be done. The @parent directive will be replaced with the content in the layout file when the view is rendered.
Note that, unlike the sidebar defined in the file layout, the subpage is ended with @endsection instead of @show. Because @endsection is only used to define blocks, and @show is used to define and immediately generate blocks.
To return the view file directly from the route, you need to use the global auxiliary function helper:
Route::get('blade', function(){
return view('child');
})3, Component & Slot
Component and slot Slots provide similar benefits to layouts and blocks. The mental model of components and slots is more intuitive. Imagine that we have a repeatable "pop-up box" component in our project:
<!-- Stored resource/views/alter.blade.php -->
<div class="alter alter-danger">
{{ $slot }}
</div>{{ $slot }} represents the content of the inserted component. To build this component, use Blade's @component directive:
@component('alter')
<strong>Whoops!</strong> Something went wrong!
@endcomponentIn this scenario, {{ $slot }} The content of the variable is:
<strong>Whoops! </strong> Something went wrong!
Sometimes one Components require multiple slots. At this time, you only need to slightly change the component code and define a "title" slot, which is called a named slot. Named slots display content by simply "printing" the variable matching its name:
<!-- Stored resources/views/alter.blade.php-->
<div class="alter alter-danger">
<div class="alter-title">{{ $title }}</div>
{{ $slot }}
</div>To inject content into a named slot, use the @slot directive. All content not in the @slot directive will be passed to the $slot variable in the component.
@compontent ('alter')
@slot('title')
Forbidden
@endslot
You are not allowed to access this resource!
@edcompontent~4. Pass additional data for the component:
Sometimes it is necessary to pass additional data for the component. To do this, you can pass a second array argument to the @conponent directive. Specify extras to pass. All past additional data can be used as variables in the component template:
@component
<compontent('alter', ['foo' => 'bar');
.....
@endCompontent5. Display data
Transfer data to the Blade view by passing The variable is wrapped in [ ] :
Route::get('greeting', function(){
return view('welcome', [ 'name' => ''Samantha']);
})You can use the name variable to display the content:
Hello! {{ $name }}{{ }} Yes Blade view's print statement. Of course, the print statement is not limited to printing variable contents, and PHP functions can also be used. In fact, any PHP code can be used in the print statement here:
The current UNIX timestamp is {{ time() }}6. Display non-transferred data
By default, all is passed to Blade {{ }} The content of the statement will be processed using the htmlspecialchar function to escape the content to avoid XSS attacks. If there is no need to escape the output content, you can use the following syntax:
Hello! {{!! $name !!}}.But be careful, you should give priority to using the escaped {{ }} syntax to avoid XXS attacks. Because sometimes it is difficult to avoid intentional or unintentional data input by users.
Related learning recommendations: Laravel
The above is the detailed content of What is a Blade template?. 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
1378
52
Comparison of the latest versions of Laravel and CodeIgniter
Jun 05, 2024 pm 05:29 PM
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.
How do the data processing capabilities in Laravel and CodeIgniter compare?
Jun 01, 2024 pm 01:34 PM
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
Laravel - Artisan Commands
Aug 27, 2024 am 10:51 AM
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 ?
Which one is more beginner-friendly, Laravel or CodeIgniter?
Jun 05, 2024 pm 07:50 PM
For beginners, CodeIgniter has a gentler learning curve and fewer features, but covers basic needs. Laravel offers a wider feature set but has a slightly steeper learning curve. In terms of performance, both Laravel and CodeIgniter perform well. Laravel has more extensive documentation and active community support, while CodeIgniter is simpler, lightweight, and has strong security features. In the practical case of building a blogging application, Laravel's EloquentORM simplifies data manipulation, while CodeIgniter requires more manual configuration.
Laravel vs CodeIgniter: Which framework is better for large projects?
Jun 04, 2024 am 09:09 AM
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.
Questions and Answers on PHP Enterprise Application Microservice Architecture Design
May 07, 2024 am 09:36 AM
Microservice architecture uses PHP frameworks (such as Symfony and Laravel) to implement microservices and follows RESTful principles and standard data formats to design APIs. Microservices communicate via message queues, HTTP requests, or gRPC, and use tools such as Prometheus and ELKStack for monitoring and troubleshooting.
Laravel vs CodeIgniter: Which framework is better for small projects?
Jun 04, 2024 pm 05:29 PM
For small projects, Laravel is suitable for larger projects that require strong functionality and security. CodeIgniter is suitable for very small projects that require lightweight and ease of use.
Which is the better template engine, Laravel or CodeIgniter?
Jun 03, 2024 am 11:30 AM
Comparing Laravel's Blade and CodeIgniter's Twig template engine, choose based on project needs and personal preferences: Blade is based on MVC syntax, which encourages good code organization and template inheritance. Twig is a third-party library that provides flexible syntax, powerful filters, extended support, and security sandboxing.
