Weave Code
Filament Rating Field Laravel Package
yepsua/filament-rating-field
A Filament form field that adds interactive star ratings to your admin panels. Let users rate with a simple, customizable stars component for forms and tables.
yepsua/filament-rating-field adds a polished star-rating input to Laravel Filament forms. Use it for reviews, feedback, satisfaction scores, or any numeric rating with a fluent API that feels native to Filament.
- Drop-in RatingField form component
- Customizable star count, icons, colors, and size
- Supports read-only display and interactive input
- Integrates cleanly with Filament validation and form state
Frequently asked questions about Filament Rating Field
- What is yepsua/filament-rating-field and what is it used for?
- It is a single-purpose Filament form field component that adds an interactive star rating input to forms built with the Filament schema builder. You drop it into a ->schema([...]) array next to TextInput, Select, and other fields, and it renders a Livewire-bound control that stores whatever scalar value you bind to it. Typical uses are product reviews, satisfaction scores, and feedback forms in a Laravel admin panel. It does not touch your domain, persistence, auth, or routing layers.
- Which Filament and Laravel versions does yepsua/filament-rating-field support?
- You must check the package's composer.json constraints rather than trusting the repository metadata. Because the field extends Filament\Forms\Components\Field, it inherits every breaking change in that base class, and Filament's form APIs moved materially between v3 and v4. Confirm the constraint matches your pinned Filament version exactly, and that you are on Laravel 10 or 11 with PHP 8.1+ and Livewire 3 before installing.
- How do I install yepsua/filament-rating-field in a Laravel app?
- Install it with composer require yepsua/filament-rating-field, then optionally register the plugin in your Filament PanelProvider if the package ships one. After that, declare the field inside the target form schema. The integration surface is roughly three lines, the license is MIT, and the blast radius is a single form component, so it can be validated end-to-end in an afternoon against a real form and a real Eloquent model.
- Does the rating field support half-star or fractional ratings and read-only display?
- The package advertises half-star precision, so fractional values are supported, but verify the exact behavior in the README for your installed version. If you store fractions, use a decimal column such as decimal(2,1) rather than an integer, and make sure validation allows the fractional step. Read-only display mode is worth confirming too, since many teams want to show an average rating without an editable input.
- Does the package handle validation and database storage for ratings?
- Treat the field as presentation only and own the schema and rules yourself. Add validation such as ->required()->numeric()->min(1)->max(5) in the form and define the migration column type that matches your data, whether that is an unsigned tiny integer for whole stars or a decimal for halves. Do not let a third-party widget dictate your storage contract. Check whether the package ships any cast, migration helper, or validation rule you would be implicitly adopting.
- Does it publish CSS or Alpine assets, and can that break my deployment?
- Check whether the package registers its own assets or relies entirely on Filament's existing Tailwind build. If it publishes CSS or JavaScript, your deploy pipeline must run filament:assets or vendor:publish, and a missing step is a deployment-time failure mode. Packages that lean on Filament's build are lower risk and generally theme correctly in dark mode. Confirm the behavior on a staging deploy before rolling to production.
- Is yepsua/filament-rating-field safe to use in production?
- Runtime risk is low because the package is a small UI widget with no domain, persistence, or queue concerns, but bus-factor risk is real: it has around 47 stars, single-vendor provenance, and no public dependents, so you would be the first meaningful production consumer. That is acceptable for a roughly 200-line form control, not for anything you would call infrastructure. The compensating factor is a near-zero exit cost: worst case you fork, vendor, or reimplement it with Alpine in about a day.
- How do I customize the icons and colors of the star rating field?
- The package advertises customizable icons and colors, typically exposed as chainable field methods or via Filament's existing color and icon APIs. Read the README for the exact method names on your installed version, since these change between releases. If the built-in options are too limited, you can subclass the field or override its Blade view, which is straightforward because the component is small and isolated. Keep customizations in your own class so package upgrades do not overwrite them.
- How do I test a Filament form that uses the rating field?
- Test through Filament's own form testing helpers rather than asserting on rendered HTML. Use fillForm with the field's state path, then assert the underlying model or form state received the expected scalar, and add a Livewire component test for any custom validation. If half-star values matter, include a case with a decimal like 3.5 to prove the round-trip survives storage. This also verifies the field binds correctly on your Filament version.
- What are the alternatives to yepsua/filament-rating-field?
- You can build a custom Field subclass with Alpine and Tailwind in about a day, use a broader Filament plugin suite that bundles richer widgets, or wire a generic star-rating JavaScript component through Alpine. Given the small scope of the feature, in-house implementation is realistic, especially if you need read-only display, fractional ratings, or a storage contract the package does not support. Only consider this package at all if your admin surface is already Filament.
Weaver
How can I help you explore Laravel packages today?