- How do I install and use filament-timepicker in a Laravel Filament app?
- Install it with composer require husam-tariq/filament-timepicker, then import HusamTariq\FilamentTimePicker\Forms\Components\TimePickerField in your Filament form. Use TimePickerField::make('from_hour')->label('time')->okLabel('Confirm')->cancelLabel('Cancel'). The package adds a form field only; no migrations or extra service provider setup are described beyond normal Filament package registration.
- Which Filament versions does filament-timepicker support?
- The changelog indicates v4.0.0 adds Filament v4 support and v3.0.x targets Filament v3. Filament v2 or untested minor lines are not explicitly covered, so verify the released tag's composer.json constraints against your installed Filament version. Do not rely on the changelog headline alone.
- How do I change the confirm and cancel button labels?
- Chain okLabel() and cancelLabel() on the field, as in TimePickerField::make('from_hour')->okLabel('Confirm')->cancelLabel('Cancel'). These labels customize the modal picker's confirm and cancel actions. The README does not document additional label options beyond these methods.
- Can I customize the time picker's Blade view?
- Yes. Publish the package views with php artisan vendor:publish --tag="filament-timepicker-views", then edit the published Blade files. This lets you adjust the picker markup without forking the package. Re-publish or merge changes carefully after package updates.
- How does filament-timepicker compare to Filament's built-in TimePicker?
- Filament v3 and v4 already include a native TimePicker field, so this package's main differentiator is its modal-style UX, okLabel/cancelLabel support, and configurable suffix icon. If your requirement is only time entry, compare the native field first. Prefer native unless the labels, icon, or modal presentation are essential.
- Does filament-timepicker handle timezones or time formats?
- The README does not document timezone handling, format() or displayFormat() behavior, or how the value is interpreted. A time-only value has no intrinsic offset, so timezone correctness is likely your application's responsibility. Define whether you store UTC and convert at render or store naive local time, and test against Filament::getTimezone() and config('app.timezone').
- What value does TimePickerField save to the model?
- The README does not state the exact string or shape written to the model on save. Test the field with your statePath, especially inside repeaters, relation managers, and modal forms, because past releases fixed state-path and validation defects. Confirm the serialized value is stable across Filament minor updates before relying on it.
- Does TimePickerField support validation like min/max time or minute steps?
- Validation appears to inherit from Filament's base field, and the README documents no min/max time, step, or range support. Business rules such as 'must be between 09:00 and 17:00' will need custom validation rules. Minute-step granularity and 24-hour input are also not documented, so verify them in your Filament version.
- Is filament-timepicker safe for production and actively maintained?
- The package has a single maintainer, roughly 33 stars, and zero dependents, so there is little visible production validation. Its release history includes corrective patches for validation, statePath, and suffixIcon issues, which suggests budgeting for maintenance across Filament minor releases. For a small UI wrapper this may be acceptable, but avoid putting it on a revenue-critical time-entry path without a fallback or fork plan.
- Does the modal time picker support keyboard input and accessibility?
- The README does not describe keyboard-only entry, focus trapping, ARIA labels for okLabel/cancelLabel, or typed input support. Before adopting it, test the modal picker with keyboard navigation and a screen reader in your target browsers. If accessibility is a hard requirement, confirm these behaviors or prefer a native or custom field you can fully control.