- What is archilex/filament-toggle-icon-column used for?
- It adds a clickable icon column to Filament tables for toggling boolean values inline. It is intended for Laravel admin panels already using Filament, not public APIs or core workflows. It helps admins update boolean fields quickly with customizable icons, colors, tooltips, and confirmation prompts.
- How do I install and use the Filament toggle icon column?
- Install the package with Composer and add the toggle icon column to a Filament resource table. Verify that the column renders and writes the expected boolean value in a staging admin panel. Because exact registration syntax may vary by Filament version, follow the README for your installed version.
- Which Filament and Laravel versions does this package support?
- The provided release notes only confirm that v3.2.0 adds Laravel 12 support; they do not list exact Filament or PHP constraints. Check the package's composer.json and README for declared filament/filament, laravel/framework, and php constraints before installing. Match the package to your application's Filament major version, not just its Laravel version.
- Does this package support Laravel 12?
- Version 3.2.0 adds Laravel 12 support and dependency updates, so it is the baseline for Laravel 12 adoption. Confirm your PHP and Filament versions also satisfy the package's composer.json constraints. Test the column in a branch before rolling it out to production.
- Is v3.2.0 a drop-in upgrade from v3.1.1?
- Release notes do not indicate breaking API changes, so it appears to be a low-risk patch or minor upgrade from v3.1.1. Still verify Composer constraints for Laravel, PHP, and Filament and run your application tests. Manually check toggle rendering, writes, authorization, validation, and null states in staging.
- Does the toggle icon column enforce Filament authorization policies?
- The package is a Filament admin UI column and should not be treated as an authorization layer by itself. Configure Filament policies and any host-application checks so users cannot toggle records they should not edit. Validate authorization behavior in tests, especially for sensitive boolean fields.
- Is there audit logging or an event dispatched when a boolean is toggled?
- The available release context does not indicate built-in audit logging or state-change event dispatch. If the boolean change is audit-sensitive, add host-application logging or model events and test them. Do not rely on the icon column alone for regulated or high-stakes state changes.
- Are icon-only toggles accessible for screen readers and keyboard users?
- Icon-only toggles can be hard for screen readers and keyboard users unless labels, tooltips, and focus behavior are handled well. Use the package's tooltip customization and test with keyboard navigation and assistive technology. Treat accessibility as an application-level concern and verify it in your Filament admin panel.
- Can I customize the on/off icons, colors, tooltips, and confirmation prompts?
- The package is designed to let you customize on/off icons, colors, tooltips, and confirmation prompts. Use those options to make toggles clear and reduce accidental changes. Check the README for exact method names and configuration syntax for your Filament version.
- What are the production risks or alternatives for boolean toggles in Filament?
- Main risks include Filament major-version coupling, UI-only toggling without built-in authorization or audit semantics, and accessibility gaps for icon-only controls. Mitigate with staging validation, policy tests, audit logging where required, and a fallback plan for non-critical admin UX only. For high-stakes workflows, consider a standard Filament form action with explicit save and authorization instead of optimistic inline toggling.