New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
formatStateUsing Section empty field #12458
Comments
I started to look inside Filament for the first time, so I am not able to fix yet. What I found is the value is nulled in the
The third section does not have a default state, so the all Form state is nulled, overwriting the data of second section. |
Related issue. correct rendering occurs only for the last element in the list. everything on top breaks protected function getFormSchema(): array
{
return [
Tabs::make()
->tabs([
Tabs\Tab::make('')->schema([
Forms\Components\DatePicker::make('startDate')->native(false)
->afterStateUpdated(fn (Get $get) => $this->dispatch('statistics-dates', $get('startDate')))
->live()
,
Forms\Components\Section::make()->schema([
Forms\Components\Livewire::make(SalesQuantityChart::class)
]),
Forms\Components\Livewire::make(SalesQuantity::class),
]),
Tabs\Tab::make('')
]),
];
} filament 3 cannot process complex pages. widgets and tabs should have more settings |
Update: if you add another component at the start of the Form, with this code:
it works. |
Very silly thing to say, especially when you don't provide any more details |
Original issue fixed in #12819 |
Package
filament/filament
Package Version
v3.2.71
Laravel Version
v11.4.0
Livewire Version
v3.4.10
PHP Version
PHP 8.2.18
Problem description
if you add a section after another section, then the formatStateUsing method does not work, the field is empty
how to fix this?
Expected behavior
the architecture of the form should not affect the operation of the formatStateUsing method
Steps to reproduce
create a section with the formatStateUsing method
and create the next section after it
Reproduction repository
https://github.com/POMXARK/bug-filament-formatStateUsing
Relevant log output
No response
The text was updated successfully, but these errors were encountered: