I'm finding that when people use the Table-Column or Table-wide search, the debounce of 500ms is triggering a search much sooner than people are ready.
The component seems to have the debounce hard-coded, and no hooks to intercept it.
Are there any workarounds someone can offer? Or is it only fixable by a core code change? (or the unthinkable importing of the component and overriding it in-app)?
A collection of beautiful full-stack components for Laravel. The perfect starting point for your next app. Using Livewire, Alpine.js and Tailwind CSS. - filamentphp/filament