- What is icetalker/filament-stepper used for?
- icetalker/filament-stepper is a Filament form component that provides a number input with stepper controls for Laravel applications. It is intended for Filament admin or internal forms where users increment or decrement numeric values, not as a general Laravel number-input library. Keep validation, persistence, and business rules in your application code.
- How do I install filament-stepper in a Laravel Filament project?
- Install it with Composer using composer require icetalker/filament-stepper, then reference the field in a Filament form schema. Filament packages typically use service-provider auto-discovery, but confirm the package's installation notes and pin a version. Test the install in a branch or staging environment before production.
- Which Filament and Livewire versions does filament-stepper support?
- The package is built for Filament forms, so compatibility depends on your Filament major version and Livewire version. Check the package's Composer constraints and README for the exact supported matrix, including PHP and Laravel versions. Do not assume compatibility from the release date; verify in an environment that matches production.
- Can I use filament-stepper without Filament, in plain Blade or standalone Livewire?
- No. filament-stepper is a Filament form field rather than a standalone Blade or Livewire component. It only makes sense in an application that already uses Filament for admin or internal forms. If you use plain Blade or Livewire without Filament, use a native numeric input instead.
- Does the filament-stepper field support min, max, step size, and decimal precision?
- Those numeric behaviors must be verified against the current release documentation and source because the package is a small component with limited public detail. Check whether min, max, step, decimal precision, nullable values, and disabled or readonly states are supported. If a behavior is missing, wrap the field or fall back to Filament's native numeric input.
- Can filament-stepper build multi-step wizards for onboarding or checkout?
- The package is primarily a number input stepper for Filament forms, and its description also mentions guided multi-step-style navigation with labels, icons, and a progress indicator. Confirm in the source whether it provides full multi-step form wizards or only numeric step controls. For complete onboarding or checkout wizards, use Filament's native wizard features or a dedicated wizard package.
- Does filament-stepper work with Laravel validation and nullable numeric values?
- The field should map to the same underlying numeric attribute, so your existing Laravel validation rules can remain unchanged in principle. Test nullable values, validation messages, and form state serialization to confirm they behave like the field you are replacing. Server-side validation and persistence must stay in application code, not in the presentation component.
- Is filament-stepper accessible by keyboard and screen reader on mobile?
- Accessibility is not guaranteed by the package description, so test keyboard entry, screen-reader announcements, and mobile touch interaction explicitly. Also check rapid increment and decrement clicks for Livewire state synchronization issues. If accessibility gaps appear, wrap the component or use a native numeric input.
- Do I need to publish assets or register a service provider for filament-stepper?
- Filament plugins often rely on service-provider auto-discovery, but you should confirm the package's installation steps. Check whether any assets must be published, especially if you use a custom Filament theme or production asset build. A quick staging install will reveal service-provider, asset, and rendering issues early.
- Is filament-stepper actively maintained, and what should I do if it is abandoned?
- The package has a small footprint and an MIT license, which lowers replacement risk, but its community and maintainer base appear thin. Review release history and maintainer response times, and pin the version you validate. If it is abandoned or breaks with a Filament or Livewire upgrade, fork it or replace it with Filament's native numeric input behind a local field wrapper.