[Feature Request]: Persist filters in getTableStateToArray() and restoreStateFromArray()

[rpcanter]

Overview

We're currently implementing a filter preset system that stores the result of getTableStateToArray() and later restores it with restoreStateFromArray().

Most table state (search, sort, pagination, column visibility, etc.) is included out of the box, but filters are missing.

Detailed explanation

Could you consider:

Including the currently active filters (e.g. appliedFilters) in the output of getTableStateToArray()

Making restoreStateFromArray() apply these filters via setFilter() or equivalent

Notes

No response

[lrljoe]

To avoid any unexpected changes, I think adding a method to include this for v3 would be cleanest.
e.g.
getTableStateWithFiltersToArray

or similar.

I'm just keen not to introduce anything unexpected in a minor version.

Any objection to that approach?

[rpcanter]

Happy to wait for a getTableStateWithFiltersToArray() method in a future v3.x release.

In the meantime, is there any temporary workaround you’d recommend for capturing the current filter state (e.g. via component state or hooks) so we can manually persist and restore it?

[lrljoe]

If it's just temporary store/restore, then you could enable the session storage for filters, and then restore from that.

https://rappasoft.com/docs/laravel-livewire-tables/v3/filters/available-component-methods#content-storefiltersinsessionenabled

Then you would just call

        $this->restoreFilterValues();

[lrljoe]

My v4 build does address this,but I'm looking at back porting it for the interim.

What the back port will likely consist of is a new property determining whether to bundle or not, and a new method to serialise the filters (based on the aforementioned)

[rpcanter]

Thanks for the update, great to hear that v4 addresses this. A backport solution would definitely help me.