What is the `@inject` directive in Blade?

The @inject directive in Blade is a convenient way to access services or classes directly within your Blade templates, leveraging Laravel’s service container. Instead of manually passing dependencies to views, you can inject them where needed.

Syntax:

Example

@inject('variable', 'ClassOrService')

variable: The variable name you want to use in the Blade template.
ClassOrService: The fully qualified class name (FQCN) or service alias you want to inject.

How it Works:

When you use the @inject directive, Blade resolves the class or service from Laravel’s service container and makes it available for use as the variable you’ve defined. This makes dependency injection seamless within Blade templates without modifying the controller or routes.

Example Use Case:

Imagine you have a service class called App\Services\UserStats that calculates user statistics like total posts or comments. Instead of passing this service to the view through a controller, you can inject it directly into your Blade file.

Example:

Service Class (App\Services\UserStats.php):

Example

<?php
namespace App\Services;

class UserStats
{
    public function totalPosts($userId)
    {
        // Let's assume this method returns the total posts by a user.
        return \App\Models\Post::where('user_id', $userId)->count();
    }

    public function totalComments($userId)
    {
        // Returns the total comments by a user.
        return \App\Models\Comment::where('user_id', $userId)->count();
    }
}
?>

Blade Template (profile.blade.php):

Example

@inject('userStats', 'App\Services\UserStats')

<h1>User Profile</h1>

<p>Total Posts: {{ $userStats->totalPosts($user->id) }}</p>
<p>Total Comments: {{ $userStats->totalComments($user->id) }}</p>

In this example:

The UserStats service is injected as $userStats.
You can now call the service methods directly in your Blade template, such as $userStats->totalPosts($user->id).

Benefits of `@inject`:

Separation of concerns: Keeps logic related to services out of the controller.
Simplicity: Easily inject services or dependencies without altering the method signatures or controller structure.
Clean Templates: Makes the code cleaner in cases where a view needs a service that doesn’t necessarily belong in the controller.

Another Example: Injecting a Lifecycle Service

Suppose you have a service that tracks an application’s lifecycle:

Service Class (App\Services\Lifecycle.php):

Example

<?php
namespace App\Services;

class Lifecycle
{
    public function currentStage()
    {
        return 'Production';
    }
}
?>

Blade Template (dashboard.blade.php):

Example

@inject('lifecycle', 'App\Services\Lifecycle')

<h2>Application Stage: {{ $lifecycle->currentStage() }}</h2>

Here, the Lifecycle service is available as $lifecycle, and you can display the current stage of the application directly in the Blade template.

When to Use `@inject`:

When you need a service or class in only one or a few views.
For services that don’t need to be passed to multiple views via a controller.
When you want to reduce the complexity of controllers by removing unnecessary dependencies.

This approach provides flexibility and makes your views more self-sufficient while maintaining the power of Laravel’s service container.

What is the `@inject` directive in Blade?

Syntax:

Example

How it Works:

Example Use Case:

Example

Example

Benefits of @inject:

Another Example: Injecting a Lifecycle Service

Example

Example

When to Use @inject:

Related Questions & Topics

Benefits of `@inject`:

When to Use `@inject`: