Dependency injection

[LuccaRomanelli]

Package

Other

Package Version

v3.2.96

How can we help you?

Is it possible to crate constructors in my filament classes so laravel can deal with dependecy injection?

[RuchikaTalele12]

Yes, it's possible to use constructors in your Filament classes, but with a bit of caution. Since Filament is built on top of Livewire, which has its own component lifecycle, overriding the constructor (__construct) directly isn’t the best way to handle dependency injection.

So what’s the right way?

The recommended approach is to use the mount() or boot() methods instead of the constructor. Laravel can inject your services into those methods just fine.

Example using mount():

protected MyService $myService;

public function mount(MyService $myService)
{
    $this->myService = $myService;
}

Or in boot():

protected MyService $myService;

public function boot(MyService $myService)
{
    $this->myService = $myService;
}

This keeps things clean and fully compatible with Livewire’s lifecycle.

---

What if I really want to use the constructor?

You technically can, but you must call parent::__construct() inside it. Otherwise, Filament or Livewire might break in weird ways.

public function __construct(MyService $myService)
{
    $this->myService = $myService;
    parent::__construct(); // Don't forget this!
}

That said, unless there's a very specific reason, it’s better to avoid this and just stick with mount() or boot().

---

Bonus Tip:

If you just need a quick service instance, you can always do:

$this->myService = app(MyService::class);

TL;DR

Laravel can handle DI in Filament classes — just inject your dependencies into mount() or boot() instead of the constructor. It plays much nicer with Livewire and avoids potential bugs.