These directives function identically to their PHP counterparts:. In addition to the conditional directives already discussed, the isset and empty directives may be used as convenient shortcuts for their respective PHP functions:. The auth and guest directives may be used to quickly determine if the current user is authenticated or is a guest:. If needed, you may specify the authentication guard that should be checked when using the auth and guest directives:.
You may check if the application is running in the production environment using the production directive:. Or, you may determine if the application is running in a specific environment using the env directive:. You may determine if a template inheritance section has content using the hasSection directive:. You may use the sectionMissing directive to determine if a section does not have content:. Switch statements can be constructed using the switch , case , break , default and endswitch directives:.
In addition to conditional statements, Blade provides simple directives for working with PHP's loop structures. Again, each of these directives functions identically to their PHP counterparts:. When using loops you may also end the loop or skip the current iteration using the continue and break directives:. This variable provides access to some useful bits of information such as the current loop index and whether this is the first or last iteration through the loop:. The class directive conditionally compiles a CSS class string.
The directive accepts an array of classes where the array key contains the class or classes you wish to add, while the value is a boolean expression. If the array element has a numeric key, it will always be included in the rendered class list:. Blade's include directive allows you to include a Blade view from within another view. All variables that are available to the parent view will be made available to the included view:.
Even though the included view will inherit all data available in the parent view, you may also pass an array of additional data that should be made available to the included view:. If you attempt to include a view which does not exist, Laravel will throw an error. If you would like to include a view that may or may not be present, you should use the includeIf directive:. If you would like to include a view if a given boolean expression evaluates to true or false , you may use the includeWhen and includeUnless directives:.
To include the first view that exists from a given array of views, you may use the includeFirst directive:. The each directive's first argument is the view to render for each element in the array or collection. The second argument is the array or collection you wish to iterate over, while the third argument is the variable name that will be assigned to the current iteration within the view.
So, for example, if you are iterating over an array of jobs , typically you will want to access each job as a job variable within the view.
The array key for the current iteration will be available as the key variable within the view. You may also pass a fourth argument to the each directive. This argument determines the view that will be rendered if the given array is empty. If the child view requires these variables, you should use the foreach and include directives instead. The once directive allows you to define a portion of the template that will only be evaluated once per rendering cycle.
This may be useful for pushing a given piece of JavaScript into the page's header using stacks. For example, if you are rendering a given component within a loop, you may wish to only push the JavaScript to the header the first time the component is rendered:.
In some situations, it's useful to embed PHP code into your views. You can use the Blade php directive to execute a block of plain PHP within your template:. Blade also allows you to define comments in your views. Components and slots provide similar benefits to sections, layouts, and includes; however, some may find the mental model of components and slots easier to understand.
There are two approaches to writing components: class based components and anonymous components. To create a class based component, you may use the make:component Artisan command. To illustrate how to use components, we will create a simple Alert component. The make:component command will also create a view template for the component. However, if you are building a package that utilizes Blade components, you will need to manually register your component class and its HTML tag alias.
You should typically register your components in the boot method of your package's service provider:. Alternatively, you may use the componentNamespace method to autoload component classes by convention.
This will allow the usage of package components by their vendor namespace using the package-name:: syntax:. Blade will automatically detect the class that's linked to this component by pascal-casing the component name.
Subdirectories are also supported using "dot" notation. To display a component, you may use a Blade component tag within one of your Blade templates. Blade component tags start with the string x- followed by the kebab case name of the component class:. Hard-coded, primitive values may be passed to the component using simple HTML attribute strings. PHP expressions and variables should be passed to the component via attributes that use the : character as a prefix:.
You should define the component's required data in its class constructor. All public properties on a component will automatically be made available to the component's view.
It is not necessary to pass the data to the view from the component's render method:. When your component is rendered, you may display the contents of your component's public variables by echoing the variables by name:. Component constructor arguments should be specified using camelCase , while kebab-case should be used when referencing the argument names in your HTML attributes.
For example, given the following component constructor:. Since some JavaScript frameworks such as Alpine. For example, given the following component:. In addition to public variables being available to your component template, any public methods on the component may be invoked.
For example, imagine a component that has an isSelected method:. You may execute this method from your component template by invoking the variable matching the name of the method:. Blade components also allow you to access the component name, attributes, and slot inside the class's render method. However, in order to access this data, you should return a closure from your component's render method.
This array will contain several elements that provide information about the component:. The attributes element will contain all of the attributes that were present on the HTML tag. The closure should return a string. If the returned string corresponds to an existing view, that view will be rendered; otherwise, the returned string will be evaluated as an inline Blade view. If your component requires dependencies from Laravel's service container , you may list them before any of the component's data attributes and they will automatically be injected by the container:.
We've already examined how to pass data attributes to a component; however, sometimes you may need to specify additional HTML attributes, such as class , that are not part of the data required for a component to function. Typically, you want to pass these additional attributes down to the root element of the component template. For example, imagine we want to render an alert component like so:. All of the attributes that are not part of the component's constructor will automatically be added to the component's "attribute bag".
All of the attributes may be rendered within the component by echoing this variable:. Sometimes you may need to specify default values for attributes or merge additional values into some of the component's attributes.
To accomplish this, you may use the attribute bag's merge method. This method is particularly useful for defining a set of default CSS classes that should always be applied to a component:. Sometimes you may wish to merge classes if a given condition is true. You can accomplish this via the class method, which accepts an array of classes where the array key contains the class or classes you wish to add, while the value is a boolean expression.
If you need to merge other attributes onto your component, you can chain the merge method onto the class method:. When merging attributes that are not class attributes, the values provided to the merge method will be considered the "default" values of the attribute. However, unlike the class attribute, these attributes will not be merged with injected attribute values. Instead, they will be overwritten. For example, a button component's implementation may look like the following:.
To render the button component with a custom type , it may be specified when consuming the component. If no type is specified, the button type will be used:. If you would like an attribute other than class to have its default value and injected values joined together, you may use the prepends method. In this example, the data-controller attribute will always begin with profile-controller and any additional injected data-controller values will be placed after this default value:.
You may filter attributes using the filter method. This method accepts a closure which should return true if you wish to retain the attribute in the attribute bag:. For convenience, you may use the whereStartsWith method to retrieve all attributes whose keys begin with a given string:. Conversely, the whereDoesntStartWith method may be used to exclude all attributes whose keys begin with a given string:.
Using the first method, you may render the first attribute in a given attribute bag:. If you would like to check if an attribute is present on the component, you may use the has method. This method accepts the attribute name as its only argument and returns a boolean indicating whether or not the attribute is present:. By default, some keywords are reserved for Blade's internal use in order to render components.
The following keywords cannot be defined as public properties or method names within your components:. You will often need to pass additional content to your component via "slots". To explore this concept, let's imagine that an alert component has the following markup:. Sometimes a component may need to render multiple different slots in different locations within the component.
Let's modify our alert component to allow for the injection of a "title" slot:. You may define the content of the named slot using the x-slot tag. If you have used a JavaScript framework such as Vue, you may be familiar with "scoped slots", which allow you to access data or methods from the component within your slot.
In this example, we will assume that the x-alert component has a public formatAlert method defined on its component class:. Like Blade components, you may assign additional attributes to slots such as CSS class names:. To interact with slot attributes, you may access the attributes property of the slot's variable. For more information on how to interact with attributes, please consult the documentation on component attributes :. Each piece is available in three different rarity levels, blue, gold, and purple.
The higher the difficulty, the better the chances of getting rare loot! Dungeon Changes: The number of possible instances has been adjusted.
Although many challenges close their gates, old, familiar acquaintances, like the Abscess and Velik's Hold, make a grand return. Kaia's Soul Rewards: Players with enchanted Kaia's Soul gear will be sent rewards upon the release of patch These rewards apply separately per character and will vary depending on their current enchantment level. Players could receive rewards ranging from enchantment gold, Blessings of the Goddess, and shiny titles.
More Content: Patch will see several quality-of-life improvements as well! Campfires make a glorious return, introducing a new customized function, while the patch also introduces a system for transferring different equipment values. And finally, the LFG group search will no longer be limited to the player's current server.
Enjoyed this? Please share on social media! Comments will load 8 seconds after page. Click here to load them now. Latest by Gavin Sheehan.
0コメント