ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #filamentphp
FilamentPHP Livewire AJAX failures after mixed Vite asset manifests during rolling deployment The goal is to run a small Laravel application with Filament v3 admin routes alongside legacy routes during a rolling deployment, without interrupting Livewire AJAX requests in the admin panel. Filament v3 compiles UI assets through Vite and publishes a versioned ma
Filament v3 form actions are Livewire server-side handlers that execute on every submission, so a user retrying a create or update action can trigger duplicate writes if the handler is not guarded. The framework does not provide a documented idempotency token or automatic deduplication for action invocations. On the client side, disabling the action button d
When managing FilamentPHP resources with datasets exceeding 100,000 records, the choice of pagination strategy significantly impacts both database performance and the administrative user experience. The native Table Builder supports standard offset-based pagination, which allows users to jump to specific page numbers. However, as the offset increases, query
Goal Determine which Eloquent pagination method the Filament 3.0 Table component invokes by default, and assess the impact on memory usage and hosting costs for low‑traffic sites. Context The Table component’s query builder appears to call Eloquent’s paginate() , which performs a COUNT(*) and loads the full result set for the current page. The per‑page limit
Context The filament:upgrade command in Filament v3 updates Composer dependencies and publishes configuration and asset files, but it does not rewrite application resource classes, custom form fields, or table components that rely on removed v2 base classes. At the same time, Filament's internal database tables (e.g., filament_users , filament_pages ) must b
Filament v3 tables paginate through Laravel’s paginator and expose page size through recordsPerPage() , defaulting to 15 records. Page, sort, and filter state live as Livewire component properties persisted to the session. When the same table is open in multiple browser tabs, or rapid concurrent requests target one component, those session-backed properties
livewire