Prevented dependency injection of Models (non existent?)
What was the reason for this change: https://github.com/filamentphp/filament/blame/4.x/packages/support/src/Concerns/EvaluatesClosures.php#L85
@ralphjsmit
One can restore this by binding all the models, but this goes against Laravel DI since Models can be injected without issues. A clear commit agains this. I'd like to know the reasons behind this. Thank you.
@ralphjsmit
One can restore this by binding all the models, but this goes against Laravel DI since Models can be injected without issues. A clear commit agains this. I'd like to know the reasons behind this. Thank you.
GitHub
A powerful open source UI framework for Laravel • Build and ship admin panels & apps fast with Livewire - Blaming filament/packages/support/src/Concerns/EvaluatesClosures.php at 4.x · filam...
Solution
In Filament V3 it introduced that you can now alias the injected record to another parameter name instead of
See also here: https://github.com/filamentphp/filament/pull/15160
$recordPost $postPost $recordPost $record?Post $recordPost $post$post$recordSee also here: https://github.com/filamentphp/filament/pull/15160
GitHub
Currently, the closure evaluation system works great by resolving any dependencies not provided by name or type from the container. This is very useful. However, there is one situation where it isn...
