You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that recordSelectOptionsQuery function not having search variable which is important to customize query for example using custom scope query for searching
Hey @hsul4n! We're sorry to hear that you've hit this issue. 💛
However, it looks like you forgot to fill in the reproduction repository URL. Can you edit your original post and then we'll look at your issue?
We need a public GitHub repository which contains a Laravel app with the minimal amount of Filament code to reproduce the problem. Please do not link to your actual project, what we need instead is a minimal reproduction in a fresh project without any unnecessary code. This means it doesn't matter if your real project is private / confidential, since we want a link to a separate, isolated reproduction. That would allow us to download it and review your bug much easier, so it can be fixed quicker. Please make sure to include a database seeder with everything we need to set the app up quickly.
Package
filament/filament
Package Version
v3.2
Laravel Version
v11.9.0
Livewire Version
v3.5.4
PHP Version
PHP 8.3.0
Problem description
I noticed that
recordSelectOptionsQuery
function not havingsearch
variable which is important to customize query for example using custom scope query for searchingfilament/packages/tables/src/Actions/AssociateAction.php
Line 202 in d8c326d
Expected behavior
recordSelectOptionsQuery
function must havesearch
variableSteps to reproduce
1- Add
Filament\Tables\Actions\AssociateAction::make()
action into table header actions.2- Call
$action->recordSelectOptionsQuery(fn($query, $search) => $query->customScope($search))
.Reproduction repository (issue will be closed if this is not valid)
https://github.com/filamentphp/demo
Relevant log output
No response
Donate 💰 to fund this issue
The text was updated successfully, but these errors were encountered: