Components and slots in Laravel - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to include a Blade component named 'alert'.

Laravel

<x-[1] />

Drag options to blanks, or click blank then click option'

Aheader

Blayout

Calert

Dfooter

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting the 'x-' prefix before the component name.

Using a component name that does not exist.

The Blade component is included using the syntax where 'alert' is the component name.

2fill in blank

medium

Complete the code to pass a 'type' attribute with value 'error' to the 'alert' component.

Laravel

<x-alert [1]="error" />

Drag options to blanks, or click blank then click option'

Atype

Bclass

Cid

Dslot

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'class' instead of 'type' for the attribute.

Trying to pass data inside the slot instead of as an attribute.

Attributes are passed to components as HTML attributes. Here, 'type' is the attribute name.

3fill in blank

hard

Fix the error in the component slot usage by completing the code to define a slot named 'title'.

Laravel

<x-alert>
    <x-slot name="[1]">
        Error!
    </x-slot>
</x-alert>

Drag options to blanks, or click blank then click option'

Aheader

Btitle

Cfooter

Dcontent

Attempts:

3 left

💡 Hint

Common Mistakes

Using a slot name that the component does not recognize.

Forgetting to close the tag properly.

Slots are named sections inside components. The 'title' slot is commonly used for headings.

4fill in blank

hard

Fill both blanks to pass a variable named 'message' and display it inside the default slot.

Laravel

<x-alert [1]="[2]">
    {{ $message }}
</x-alert>

Drag options to blanks, or click blank then click option'

Atype

Bmessage

Cslot

Dcontent

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'slot' or 'content' as attribute names instead of 'message'.

Passing the variable name incorrectly without quotes.

The attribute 'message' is used to pass the variable 'message' to the component, which can then display it inside the default slot.

5fill in blank

hard

Fill all three blanks to create a component with a named slot 'footer' and pass a 'color' attribute with value 'red'.

Laravel

<x-alert [1]="[2]">
    <x-slot name="[3]">
        Footer content
    </x-slot>
</x-alert>

Drag options to blanks, or click blank then click option'

Acolor

Bred

Cfooter

Dheader

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect attribute names like 'header' instead of 'color'.

Misnaming the slot or forgetting the 'name' attribute.

The 'color' attribute is set to 'red', and the named slot 'footer' is defined inside the component.

Practice

1. What is the main purpose of using components in Laravel Blade?

easy

A. To define routes for the application

B. To write raw PHP code inside Blade templates

C. To create reusable pieces of UI that can be included in multiple views

D. To connect Laravel with external databases

Solution

1. Step 1: Understand what components do

   Components in Laravel Blade are designed to hold reusable UI parts, like buttons or cards, so you don't repeat code.

2. Step 2: Compare options with component purpose

   Only To create reusable pieces of UI that can be included in multiple views describes reusable UI pieces. Other options describe unrelated tasks.

3. Final Answer:

   To create reusable pieces of UI that can be included in multiple views -> Option C

4. Quick Check:

   Components = reusable UI [OK]

Hint: Components = reusable UI blocks in Blade templates [OK]

Common Mistakes:

• Confusing components with routing or database tasks
• Thinking components are for PHP logic only
• Assuming components are only for styling

2. Which of the following is the correct syntax to pass a slot named header to a Laravel Blade component called card?

easy

A. Title

B. Title

C.

D. Title

Solution

1. Step 1: Recall named slot syntax in Blade

   Named slots use <x-slot name="slotName">...</x-slot> inside the component tags.

2. Step 2: Match syntax with options

   <x-card><x-slot name="header">Title</x-slot></x-card> correctly uses <x-slot name="header">. Others misuse slot attribute or tag.

3. Final Answer:

   <x-card><x-slot name="header">Title</x-slot></x-card> -> Option A

4. Quick Check:

   Named slot syntax = <x-slot name="name"> [OK]

Hint: Use for named slots inside components [OK]

Common Mistakes:

• Using slot attribute instead of tag
• Confusing slot with regular HTML <slot> tag
• Passing slot content as a component attribute

3. Given this Blade component usage:

<x-alert>
  <x-slot name="title">Warning</x-slot>
  This is an alert message.
</x-alert>

And the component template:

<div class="alert">
  <h4>{{ $title }}</h4>
  <p>{{ $slot }}</p>
</div>

What will be the rendered HTML output?

medium

A. WarningThis is an alert message.

B. Warning This is an alert message.

C. titleThis is an alert message.

D. Warning

Solution

1. Step 1: Understand slot and named slot usage

   The $title variable receives content from the named slot title. The default $slot holds the inner content outside named slots.

2. Step 2: Match passed content to template placeholders

   The title slot is "Warning", and the default slot is "This is an alert message." so they fill <h4> and <p> respectively.

3. Final Answer:

   <div class="alert"><h4>Warning</h4><p>This is an alert message.</p></div> -> Option A

4. Quick Check:

   Named slot fills $title, default slot fills $slot [OK]

Hint: Named slots fill variables, default slot fills $slot content [OK]

Common Mistakes:

• Confusing default slot with named slot content
• Expecting named slot content inside $slot variable
• Ignoring that $title is set by named slot

4. Identify the error in this Blade component usage:

<x-modal>
  <x-slot name="footer">Close</x-slot>
  <x-slot>Content here</x-slot>
</x-modal>

What is the problem?

medium

A. Named slots cannot be used inside components

B. The slot name "footer" is reserved and cannot be used

C. Slots must be self-closing tags

D. The unnamed slot is incorrectly declared with <x-slot> instead of using default slot syntax

Solution

1. Step 1: Check unnamed slot syntax

   The default slot content should be placed directly inside the component tags, not wrapped in <x-slot> without a name.

2. Step 2: Understand correct default slot usage

   Using <x-slot> without a name is invalid. Default slot content is just plain content inside the component.

3. Final Answer:

   The unnamed slot is incorrectly declared with <x-slot> instead of using default slot syntax -> Option D

4. Quick Check:

   Default slot = direct content, not tag [OK]

Hint: Default slot is plain content, not wrapped in [OK]

Common Mistakes:

• Wrapping default slot content in without name
• Thinking all slots must be named
• Believing slots must be self-closing

5. You want to create a reusable profile-card component that accepts a header slot for the user's name, a default slot for the bio, and a footer slot for action buttons. Which Blade component template correctly supports these slots?

hard

A.
{{ $slot }}
{{ $header }}
{{ $footer }}

B.
{{ $header }}
{{ $slot }}
{{ $footer }}

C.
{{ $header }}
{{ $footer }}
{{ $slot }}

D.
{{ $footer }}
{{ $slot }}
{{ $header }}

Solution

1. Step 1: Match slots to variables

   The named slots header and footer correspond to $header and $footer. The default slot content is in $slot.

2. Step 2: Verify correct placement in template

   <div class="profile-card"> <header>{{ $header }}</header> <section>{{ $slot }}</section> <footer>{{ $footer }}</footer> </div> places $header in <header>, $slot in <section>, and $footer in <footer>, matching the requirement.

3. Final Answer:

   <div class="profile-card"> <header>{{ $header }}</header> <section>{{ $slot }}</section> <footer>{{ $footer }}</footer> </div> -> Option B

4. Quick Check:

   Named slots = $header/$footer, default slot = $slot [OK]

Hint: Named slots = variables, default slot = $slot in template [OK]

Common Mistakes:

• Mixing up slot variable names and their placement
• Using $slot for named slots
• Placing slots in wrong HTML sections