- How do I install andrewdwallo/filament-selectify in a Laravel app?
- Install it with Composer using composer require andrewdwallo/filament-selectify. If you use a custom Filament theme or need the package views and assets locally, publish them with the package's artisan publish commands. Panel-provider registration is optional, and most projects can start using the fields immediately after installation. No migrations or model changes are required.
- Which version of filament-selectify should I use with Filament v3 or Filament v4?
- The package now ships two compatibility lines: v2.x targets Filament v3, and v3.0.0 targets Filament v4. Pin v2.0.9 if your admin panel is still on Filament v3, and only move to v3.0.0 when you are actually on Filament v4. Do not install latest blindly, because the correct version is determined by your Filament major, not by the newest tag.
- Does filament-selectify replace Filament's Select field, or can I use both?
- It provides alternative field types for toggles, radio buttons, and segmented selectors rather than forcing a global replacement. You can keep using Filament's native Select elsewhere and adopt Selectify only where a toggle or radio UI makes more sense. Reverting a single field back to Select is essentially a one-line change, which keeps the risk low.
- Does filament-selectify support validation, required, reactive, and afterStateUpdated?
- Yes. The fields extend Filament's own field classes and bind to the same underlying state path, so standard behavior like ->required(), ->reactive(), ->live(), ->afterStateUpdated(), and validation rules are inherited. You configure them the same way you configure a normal Filament field. This inheritance is why the package stays a presentation-layer convenience rather than a new form system.
- Does filament-selectify add database migrations or model changes?
- No. It is a presentation-layer plugin for Filament forms and does not touch persistence, authorization, or domain logic. It only swaps the rendering of the Select field for toggle or radio-style controls while keeping the same state path. You should not expect new tables, model traits, or service container changes.
- Do I need to publish views or assets when using filament-selectify with a custom Filament theme?
- If you run a custom Tailwind theme, you may need to publish the package's views and assets so they are included in your build. Filament v4 reworked the asset pipeline, so verify that your Tailwind content globs cover the package's v4 views. Without a custom theme, the default setup is usually enough after Composer installation.
- How do I test forms that use filament-selectify?
- Because the fields bind to the same state path as Filament's Select, you can test them with Filament's standard Livewire form testing helpers such as fillForm and assertFormSet. The package does not ship separate test utilities, so treat the fields like any other Filament field in your test suite. Include at least one test that asserts the state updates and validation fires after a selection.
- Is filament-selectify accessible enough for WCAG 2.2 AA?
- Accessibility depends on the Blade views and form component internals that carry keyboard handling, focus rings, and ARIA roles. A sign-off on the v2.x/Filament v3 line does not automatically transfer to v3.0.0 for Filament v4, because that port touched the view layer. If you have WCAG 2.2 AA obligations, audit the specific version you pin rather than the package as a whole.
- Is filament-selectify production-ready, and what is the maintenance risk?
- It is a small, MIT-licensed package with a single maintainer historically and a low star count of around 47. The v3.0.0 Filament v4 port came from an external first-time contributor, which is a positive health signal but not a succession plan. The saving grace is that the surface area is small and the fallback to Filament's native Select is a one-line change, so you are never truly blocked.
- What are the alternatives to filament-selectify, or when should I skip it?
- Filament's native Select, Toggle, Radio, and CheckboxList fields cover many of the same use cases without an extra dependency. A custom Blade field or a small view override is another option if you only need one specialized control. Skip Selectify if you are mid-migration to Filament v4 and cannot absorb a fresh compatibility line, or if standardizing on native fields is more valuable than the UI polish.