- How do I install hydrat/filament-table-layout-toggle in a Laravel Filament app?
- Install it with Composer using composer require hydrat/filament-table-layout-toggle, then register the plugin on your Filament panel provider. Individual tables are typically opted in through a trait or fluent table modifier. Because the package is small and self-contained, read the service provider, table macro or trait, and Blade view before adopting it.
- Which Filament and Laravel versions does this table layout toggle support?
- The package is a Filament panel plugin for Laravel applications, so the exact Filament major versions should be confirmed in its composer.json before adoption. Filament table internals change between major versions such as v3 and v4, and plugins that customize table rendering are especially sensitive to those upgrades. Pin Filament in your root composer.json and let Composer resolve the plugin against that pinned version.
- Does grid mode keep Filament table sorting, filtering, search, and pagination?
- The plugin is designed to let users switch between standard table rows and card-style grid views while keeping Filament's familiar filtering, sorting, and search features. However, a grid layout may not faithfully carry every table interaction, so verify pagination, bulk selection, and row actions per resource. Treat it as a presentation-layer toggle and test each table before rollout.
- How does the plugin handle custom Filament columns like images, badges, icons, and actions in grid view?
- Custom column types such as image, badge, icon, action, and bulk action columns frequently render differently or not at all in a grid layout. This is where most QA effort should concentrate. Review the plugin's Blade view and test every custom column used in the tables you opt in.
- Is the grid or table layout choice persisted per user or per session?
- The persistence behavior is not clearly specified in the package overview, so verify whether the toggle is per-session, per-user, or per-page-load. Users will notice inconsistency if the layout resets unexpectedly. If per-user persistence matters, inspect the source for preference table or session handling and confirm whether that behavior is configurable.
- Will Tailwind purge the plugin's grid CSS classes in a Filament panel?
- Filament ships compiled CSS, and plugin Blade views that emit Tailwind classes can be purged or left unstyled unless assets are published or classes are safelisted. Check how the plugin delivers assets, whether by publishing, Vite, or inline styles. Test the production build with optimized assets before relying on the grid view.
- Is hydrat/filament-table-layout-toggle safe to use in production or is it abandoned?
- The package is MIT licensed and self-contained, but its small star count and lack of dependents place it in the single-maintainer, single-purpose category. The dominant risk is project health rather than code quality, especially because Filament table internals move between major versions. Audit the service provider, table integration, and Blade view, check whether test coverage exists, and keep vendoring or forking as a realistic contingency.
- How do I roll back or disable the layout toggle for specific Filament resources?
- Enable the toggle per resource rather than panel-wide for the first release, using the plugin's trait or fluent table modifier. Rollback is generally deleting the plugin registration and the per-table opt-in usage. No database migrations or changes to existing resources beyond opting tables in are expected, so treat it like a reversible feature flag.
- Are there alternatives to this Filament grid/table layout toggle plugin?
- Alternatives include building a custom Livewire or Blade presentation for the table, forking this MIT package, or using another Filament table customization plugin if one exists for your version. Outside Filament, Nova, Backpack, and hand-rolled Livewire tables require different approaches. Evaluate whether a presentation-only layout toggle justifies adding a dependency versus maintaining a small custom view.
- Does the plugin support responsive layouts, keyboard accessibility, and translations?
- The overview does not specify responsive breakpoints, keyboard reachability of the toggle, focus management, or translation support. Test the toggle on mobile and with keyboard navigation, and check whether the visible copy is hardcoded. If accessibility or localization matters, review the Blade view and add labels or translations as needed.