Calling refreshFormData on repeater clears them
I have an action that is defined like this:
And a form that's like this:
And although the party_size field refreshes property, the event_names and comments fields become blank.
Am I doing something wrong?
I made an example repository here:
https://github.com/cloudshipco/filamentphp-repeater-refresh-bug
GitHub
GitHub - cloudshipco/filamentphp-repeater-refresh-bug: A repository...
A repository domonstrating a possible bug in filamentphp/filament - cloudshipco/filamentphp-repeater-refresh-bug
Solution:Jump to solution
use
fillForm()
instead
```php
$this->record->performSentimentAnalysisUsingAI();
$this->fillForm();...5 Replies
Solution
use
fillForm()
instead
That worked but I don't really know why. The only thing I can find about
fillForm
in the docs is in the context of modals.
Is there a bug with refreshFormData? Should I create a GitHub issue?@Leandro Ferreira just checking if you think is worth creating a GitHub issue for? I want to create "next" and "previous" buttons on my form, and I found this solution but it seems unlikely to work if refreshFormData doesn't work for repeater types.
https://github.com/filamentphp/filament/discussions/7716
GitHub
previous and next record inside form using actions? or custom field...
Any pointers is much appreciated.
What about this?
https://filamentphp.com/content/leandrocfe-navigating-filament-pages-with-previous-and-next-buttons
Filament
Navigating Filament Pages with Previous and Next Buttons by Leandro...
A collection of beautiful full-stack components for Laravel. The perfect starting point for your next app. Using Livewire, Alpine.js and Tailwind CSS.
Hmm, it looks good and the buttons appear but they don't seem to do anything. I will try to debug it.
Ah it works, I forgot to add the trait
@Leonardo what do you think about creating a GitHub issue?