appymedia
appymedia
FFilament
Created by appymedia on 1/23/2025 in #❓┊help
Reactive fields not always saving data when higher debounce value used
Hey Folks, I'm using a lot of reactive fields, lots of afterStateUpdated goodness to calculate values etc across many resources in a Filament panel. For some of my fields I've had to bump up the debounce value to stop anomalies from the server updates and the user continuing to type at the same time (for text input fields for example). Thats improved the UX and is working great to stop what the user would see as odd behaviour. It has however opened a possible scenario when if a user is very fast at creating / updating the record in question (the forms are in Filament resources) the latest state is not sent to the server and the state is not updated via afterStateUpdated and so on, the debounce value is 1000ms at the moment. I opened an issue on github which includes more details and a repro where the debounce is set to 10000ms to show the issue clearer. Just hoping someone here might have stumbled into the same and has any workarounds at all? Heres the github issue for more info... https://github.com/filamentphp/filament/issues/15356 Appreciate any help or advice anybody has, many thanks!
2 replies