Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[10.x] Clarifies issues when passing the name attribute to components #8788

Closed
wants to merge 2 commits into from
Closed

[10.x] Clarifies issues when passing the name attribute to components #8788

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
66675c1
Clarifies issues with name attribute on slots
nunomaduro May 12, 2023
887a4bf
Update blade.md
nunomaduro May 12, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions blade.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -934,6 +934,9 @@ All of the attributes that are not part of the component's constructor will auto
> **Warning**
> Using directives such as `@env` within component tags is not supported at this time. For example, `<x-alert :live="@env('production')"/>` will not be compiled.

> **Warning**
> Because of limitations on how slots are named, it is not possible to use `name` HTML attribute as the first attribute when passing attributes to the underlying component. If you want to pass this attribute, you must provide it as the second or third element. For instance, you can use `<x-slot:input class="text-input-lg" name="my_field">...`.

<a name="default-merged-attributes"></a>
#### Default / Merged Attributes

Expand Down