- What is Filament Picker used for in Laravel Filament forms?
- Filament Picker adds a picker form field to Filament that lets users search, browse, and select records from a table or modal instead of a plain dropdown. You register it in a form schema with Picker::make('field') and it inherits your existing Filament panel auth, tenancy, and scoping behavior. It is aimed at large datasets and relationship fields where a simple Select becomes unusable.
- How do I install icetalker/filament-picker?
- Install it with Composer using composer require icetalker/filament-picker, then swap one field in a form schema to Picker::make('field'). There is no Node build step, no extra runtime, and no new infrastructure to provision. Confirm first that the package's Filament constraint matches the version your panel actually runs.
- Which Laravel and Filament versions does filament-picker support?
- Check the package's composer.json constraints before adopting, since that is what determines real compatibility. The intended stack is Laravel 10, 11, or 12 with Filament v3 or v4 and Livewire 3, the standard TALL configuration. Pin the package and Filament together in composer.lock so constraint drift surfaces early rather than during an upgrade.
- How is Filament Picker different from the native Filament Select field?
- Native Select works fine for short option lists but gets awkward with large datasets and searchable relationships, which is where a table or modal picker helps. Before rolling it out broadly, pilot it side by side with the native control behind a feature flag or per-panel toggle and compare on real data volume. The exit cost is low: swapping back to Select is effectively a one-line change if you have wrapped the field.
- Is Filament Picker good for large datasets and relationship fields?
- That is exactly its stated use case: searchable, browsable selection from a table or modal rather than a long dropdown. It suits forms where users need to find a record among many or pick a related model without preloading everything into a Select. Validate it against your own data volume during a short spike rather than assuming the behavior scales identically.
- How should I wrap Filament Picker so the exit cost stays near zero?
- Create a project-local field class such as App\Filament\Fields\EntityPicker that extends Picker, or isolate usage in a Blade partial, so no form schema references the vendor class directly. If the package is abandoned or breaks, you re-point that one class to native Select instead of editing every schema. Treat it as a convenience dependency rather than a foundational one, and adopt it only behind that wrapper.
- Is icetalker/filament-picker actively maintained?
- The risk profile is dominated by maintenance rather than correctness: the package has roughly 10 stars and is effectively single-maintainer with a narrow scope. Ask the maintainer about issue turnaround, commit cadence over the last 12 months, and the policy for Filament major-version bumps. Because the source is small, you can audit it in under an hour and keep the decision reversible through a wrapper.
- Can filament-picker block a Filament major version upgrade?
- Yes, and this is the real cost: a Composer constraint conflict stalls the whole panel upgrade, not just this one field. Pin the package and Filament together in composer.lock and add Dependabot or Renovate so drift shows up early. Add a CI gate that runs composer why-not filament/filament with the next major before any upgrade, so this package's constraint never becomes a surprise blocker.
- Does Filament Picker add migrations, service providers, or security risk?
- No. It is a Livewire-backed form field that sits purely in the presentation layer, with no migrations, no persistence logic, no domain services, and no external network calls or data handling. The license is MIT, so retain the notice, and the dependency is a leaf node whose blast radius is one form field failing to render. Verify its asset and CSS behavior against any custom Filament theme, since small packages sometimes ship uncompiled styles.
- How do I test forms that use Filament Picker?
- Ask the maintainer whether there is a published test suite, a testing helper, and CI coverage against the Filament versions you run, then confirm it during your spike. Because your wrapper class is the only reference to the vendor field, you can test your own field component and swap the underlying implementation without rewriting tests. Also check searchable and relationship options, validation, and localization behavior in a scratch panel before the pilot.