Weave Code
Matrix Choice Laravel Package
lara-zeus/matrix-choice
A Laravel package for matrix-style multiple choice fields in Filament forms: let users pick answers across rows and columns in a grid, with a clean, intuitive interface for surveys, ratings, and structured selections.
Zeus Matrix Choice multiple choice grid component form for filamentPHP
Frequently asked questions about Matrix Choice
- How do I install lara-zeus/matrix-choice in a Laravel app?
- Install it with Composer using composer require lara-zeus/matrix-choice, then add the field class to a Filament form schema. No migrations, queues, or asset publishing are required because it is a presentation-layer form component. Pin the exact version you evaluate, such as 5.0.1, and read the diff before bumping.
- Does lara-zeus/matrix-choice support my Filament and Laravel versions?
- The release under review is 5.0.1, but the exact php, laravel/framework, and filament/filament constraints must be checked in the package composer.json against your application pins. The integration spike should confirm your current Filament major is supported before adoption. Do not assume compatibility from the package name alone.
- How do I hide specific options in lara-zeus/matrix-choice?
- Version 5.0.1 added the ability to hide specific options. Before relying on it for data-bearing fields, test whether hiding is presentation-only or also enforced by server-side validation. Confirm how a saved record that references a now-hidden option renders. Treat the feature as additive but verify its semantics with a test, not just the README.
- Is lara-zeus/matrix-choice safe for surveys and ratings forms?
- It is designed for matrix-style selections such as Likert scales, NPS or CSAT batteries, onboarding questionnaires, and skills self-assessments. It renders rows and columns and allows one selection per row, which fits those structured selection patterns. Because it is a UI primitive with low coupling, adoption and removal are both cheap. Validate persistence and re-rendering on a representative form before shipping.
- How does matrix-choice handle validation for hidden options?
- The package inherits the host application Livewire state and validation pipeline, but the precise behavior of hidden options is ambiguous in the 5.0.1 release notes. You must determine whether a tampered request can submit a hidden option and whether there is an authoritative allow-list. Answer this with a server-side test before the field touches any data-bearing workflow.
- How do I persist and re-render matrix-choice values in Laravel?
- The package does not own the data model or dictate persistence, so you store the selected value through your normal Filament form and Eloquent flow. Exercise the full path in a spike: render the field, select an answer, validate, persist, then re-render a saved record. That verifies both the stored shape and how saved selections display when option state changes.
- Can I use matrix-choice for a Likert scale or NPS survey in Filament?
- Yes, that is the intended use case: picking answers across rows and columns in a grid, one selection per row. It suits Likert scales, NPS and CSAT batteries, compliance checklists, priority matrices, and similar structured selections. It is a bounded UI primitive, so the rest of the survey data model remains yours. Confirm the grid renders and validates as expected for your row and column counts.
- How do I test a lara-zeus/matrix-choice field?
- Test it end-to-end on a representative Filament form: render, select, validate, persist, and re-render a saved record. Add explicit tests for hidden options if you use that 5.0.1 feature, including a tampered request that submits a hidden value. Also verify the field reacts correctly if option state depends on sibling fields such as plan or role.
- Is lara-zeus/matrix-choice actively maintained and production-ready?
- It is MIT licensed with a single primary maintainer, around 27 stars, and zero dependents, so the bus factor is effectively one. That is acceptable for a form input but not for anything owning data or auth. The small surface makes a vendoring fallback feasible, and the 5.0.1 release included CI housekeeping that is a positive maintenance signal. Pin versions and review diffs.
- What are alternatives to lara-zeus/matrix-choice for Filament grid inputs?
- You can hand-roll a custom Filament field, but matrix grids with one selection per row are expensive to build and maintain for near-zero competitive differentiation. The buy-versus-build case favors this package for bounded UI primitives. If you need stricter release discipline or broader community support, evaluate other Filament form-field packages or vendor this one given its small surface.
Weaver
How can I help you explore Laravel packages today?