Patrick Boivin
Repeater-Field should not updated
One possible solution that comes to mind would be to use a repeater that's not connected to any field or relationship. You could initialize the repeater data manually when the page is loaded, and then add a customized "save" step. Maybe
afterSave()
would be an interesting place to experiment :
https://filamentphp.com/docs/3.x/panels/resources/editing-records#lifecycle-hooks8 replies
Repeater-Field should not updated
Thanks, it makes sense. Maybe the repeater is still appropriate for your use-case after all. But I'm not sure if you can accomplish this with
->relationship()
, because it's designed to update the related item directly.8 replies
Github like field
Could this be a custom validation rule?
https://filamentphp.com/docs/3.x/forms/validation#custom-rules
4 replies
How to prepend next item instead of appending it in a Filament Repeater
Here: https://github.com/filamentphp/filament/blob/3.x/packages/forms/src/Components/Repeater.php#L173
4 replies
Table Custom Column Update.
I think if you include the button inside of the custom column view, you could do everything with Alpine.js. Add
x-data
on the column wrapper, give each field an x-model
and make the button call a livewire method though the Livewire
global object.8 replies
Autosave entire edit form with debounce
Yeah, interesting. Maybe this could be done in JS instead of
wire:poll
. You could add a custom event listener to the form to make all fields behave as "lazy", and trigger the autosave on blur
. I'm doing something similar in Peek actually. Hehe.31 replies