Optimize Filament Repeater Field to Prevent Unnecessary Queries on Livewire Requests

[siam02]

Is your feature request related to a problem? Please describe.

In FilamentPHP, every Livewire request updates the entire component, causing unnecessary queries to execute—especially when dealing with forms that depend on multiple relationships.

For example, I have a FAQs repeater field in a form with 11 relationship models. Every time I click "Add FAQ," all relationship-related fields are also updated, as observed through Laravel Telescope. This leads to 11+ unnecessary queries per action, significantly slowing down the form's responsiveness in production.

Describe the solution you'd like

A way to isolate the repeater field so that only the repeater component is updated without triggering unrelated queries. Some possible solutions:

1. Livewire Optimization: Prevent unnecessary component-wide updates when interacting with repeaters.
2. Alpine.js Enhancement: Replace the repeater’s "Add/Remove" feature with Alpine.js, allowing client-side modifications without Livewire reactivity until submission.

Describe alternatives you've considered

Currently, a workaround is to use Lazy Loading (->lazy()) for relationship fields or manually overriding dependencies, but this does not fully resolve the issue. Using Alpine.js for repeater interactions would significantly improve performance.

Additional context

This enhancement would greatly optimize complex forms with repeaters in FilamentPHP, reducing unnecessary database queries and improving user experience.