ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #filamentphp
When custom filters break Filament table pagination, the issue often lies in query ordering, eager loading timing, URL parameter handling, or cache keys. This guide walks you through diagnosing the problem, checking the query chain, and applying fixes that restore proper pagination behavior.
Filament paginates table queries by default, so slow admin tables are usually a per-row query problem, not a pagination problem. Here's how to configure page sizes, fix N+1 aggregates, and handle bulk actions honestly.
When a FilamentPHP Livewire component initiates a long‑running operation, I need the UI to stay responsive, show a loading indicator, and allow the user to cancel the operation while also guaranteeing that the process does not exceed a predefined maximum execution time. The component must clean up any background workers or queued jobs when cancellation or ti
Goal: Prevent notification spam when using FilamentPHP's Alert facade alongside Laravel's native notification channels (mail, database, broadcast) while preserving Filament's visual alerts in the admin panel. Constraints: Filament v3's Alert facade does not include a built‑in rate‑limiting mechanism, so any limit must be added manually; custom notification c
I'm using Filament's built-in ImportAction (Filament v3) to restore records from a CSV export, mapping columns to model attributes through the standard column-mapping closures. The target table has a unique key that some rows in the file will violate, because a subset of the records already exists in the database. From what I can tell, the import runs inside
Goal: Determine whether FilamentPHP’s Repeater field automatically applies validation rules defined on its child (nested) fields when validating each repeater item, or whether those rules must be explicitly declared on the repeater schema via a ‘validation’ attribute. Uncertainty: The official documentation does not specify if nested validation rules are fla
Relationship select default value timing in FilamentPHP Panels v3 Goal: Determine whether default values are set on a relationship select field before or after the afterStateHydrated callback executes in a Filament form built with Laravel 10+, Livewire v3 and Filament Panels v3. Constraints: The form uses a BelongsTo relationship select that may be nullable,
Filament Table Builder relies on Laravel's native pagination and offers a deferred loading mode that renders the table shell before fetching records. For datasets with tens of thousands of rows, standard offset-based pagination can degrade as page numbers increase. The interaction between deferred loading and deep paging is not always clear: deferred loading
When standardizing a FilamentPHP project inside Docker containers—whether through Laravel Sail or a custom compose stack—the authentication layer often becomes the least portable part of the setup. Filament provides its own login scaffolding out of the box, yet many Laravel applications already rely on Fortify or Jetstream for user management outside the adm
livewire
laravel
docker