Your configuration files are not serializable.

[arkdev1]

Livewire PowerGrid version

v6.3.0

Livewire version

v3.6.2

Laravel version

v12.3

Which PHP version are you using?

PHP 8.4

Which Theme are you using?

Tailwind

Have you published the resource files and customized them? (php artisan vendor:publish)

No

What is the problem?

The issue originates from the fact that the configuration array under filter_attributes directly contains closures that return ComponentAttributeBag objects. While this implementation works at runtime, it inherently conflicts with Laravel's configuration caching mechanism, which attempts to serialize all configuration values using var_export(). Since PHP closures are not serializable, running commands like php artisan config:cache will fail with a LogicException indicating that configuration files are not serializable. Furthermore, any attempt to refactor this into class-based callables without an explicit resolution strategy results in PowerGrid views failing to access required array keys (e.g., selectAttributes) during rendering.

In the process of addressing the serialization issue, I attempted to follow the approach suggested in PR #1898 by defining the filter_attributes configuration like this:

'filter_attributes' => [
    'input_text' => \PowerComponents\LivewirePowerGrid\FilterAttributes\InputText::class,
    'boolean'    => \PowerComponents\LivewirePowerGrid\FilterAttributes\Boolean::class,
    'number'     => \PowerComponents\LivewirePowerGrid\FilterAttributes\Number::class,
],

This change aimed to make the configuration fully serializable and compatible with php artisan config:cache, aligning with the method proposed in the mentioned PR. However, when using this pattern, PowerGrid views failed to properly resolve the callable and threw errors such as:

Undefined array key "selectAttributes"

This indicates that PowerGrid, at runtime, was attempting to use the class string directly as an array or callable without instantiating or invoking it, leading to missing attributes expected by the view components. Despite being consistent with the PR recommendation, this pattern alone wasn't sufficient to make the feature work without further adjustments to how PowerGrid resolves these filter attribute classes internally.

Code snippets

'filter_attributes' => [
    'input_text' => \PowerComponents\LivewirePowerGrid\FilterAttributes\InputText::class,
    'boolean'    => \PowerComponents\LivewirePowerGrid\FilterAttributes\Boolean::class,
    'number'     => \PowerComponents\LivewirePowerGrid\FilterAttributes\Number::class,
],

How do you expect it to work?

I would like to ask for help to properly address this issue.
It seems that the system is trying to access ['selectAttributes'] on the raw string instead of invoking the class.

Could anyone advise:

1. What is the correct way to make PowerGrid dynamically instantiate and invoke these classes when defined like this?
2. Is additional work needed in PowerGrid core to support this ::class approach?
3. Is there an official example where this pattern works end-to-end with cached config?

Any guidance or example would be highly appreciated. Thank you!

Please confirm (incomplete submissions will not be addressed)

• I have provided easy and step-by-step instructions to reproduce the bug.
• I have provided code samples as text and NOT images.
• I understand my bug report will be removed if I haven't met the criteria above.

[luanfreitasdev]

I will investigate

[arkdev1]

Hi @luanfreitasdev, thanks! I tested the PR with this code and it works — I can successfully run php artisan optimize. However, I don't see the select input rendered in the table.

return [
    Filter::datetimepicker('created_at'),
    Filter::boolean('is_mandatory'),
    Filter::inputText('name'),
    Filter::select('name')
        ->dataSource(Sports::all())
        ->optionLabel('name')
        ->optionValue('name'),
];

[luanfreitasdev]

I couldn't simulate

[arkdev1]

Maybe i'm doing something wrong. Anyway the Bug #1901 seesm resolved.
I can call php artisan optimize and it serialize the config.

[luanfreitasdev]

but I still don't understand the select problem and couldn't reproduce it.

[arkdev1]

Seems legit, i will investigate further. I will keep you posted