Will be nice to have an option to save filter selection in session

[dgillier]

I’m having multiple filters on multiple tables in multiple pages, and in most case I’m loosing my filter selection passed by url after some navigations.

So I’m wondering if having a table option to save filters selection in session will be possible ?
Thanks,
Denis

[lrljoe]

Can you give me a tighter example. Are you using the same filter name across multiple tables? Are you using the same tableName attribute on each component? Once I can find the problem, more than happy to fix it. I was considering (optional) browser side filter caching for v3, so you come back and it's exactly how you left it. In the interim, the filter statuses etc are all stored in the attribute for the table name, so you can relatively easily push/pull from that on mount.

[lrljoe]

So I had a play, and have a working example, however there's a shed load of testing that I'll need to do before its even remotely ready, so I'm not even thinking about posting the code on here, and it's definitely not ready for widespread consumption

BUT if you jump on the Discord then I'll PM you an example, and can see what you think, as you're always so helpful in raising ideas/issues :)

[dgillier]

Thanks :)
I tried to connect to discord with the link in the discussion page, but got this:

[lrljoe]

https://discord.gg/9dR8R3DwB

Think I need to update the link!

[lrljoe]

So I've got a working prototype for persisting the filters, just need to look at how long it persists for, as the table fingerprint does change sporadically.

It's now configurable in my test environment (I.e. enable or disable the feature), and it seems to persist for a time, including hammering the back button and then browsing manually back to the correct page with the table.

I do need to test across all of the types of filters, but I don't see why it'd suddenly not work.

It'll probably be a month or so before it's in a release due to the tests and docs, but feel free to DM me on discord and I'll point you at which fork and branch it's currently in.

[lrljoe]

You'll be pleased to know that Tables v3 uses a slightly different approach (using Livewire 3), and the filters do actually track correctly with the back button.

I am still going to add the option to persist the filter values in the session, as it may be useful to someone!

[lrljoe]

It crossed my mind that you could actually do this within your table component if you have a pressing need by reading/writing from the variable that the filter values are stored in:

$this->{$this->tableName}['filters']

Not ideal, but will probably do for the interim while we finish off v3.

[dgillier]

Oh great :)
Thanks a lot, sorry, I was not very active this last month!

[lrljoe]

No problem, your absolute best bet would be to run it at boot, ideally in a trait to allow re-use.

There is actually code in the package for persisting it to a database, as when you use the reorder function, that is how it restores where you were.

Using that as a jumping off point, something like this would allow you to save the exact state of the table, which page, column select, the works:

        session([' **ADD A UNIQUE KEY HERE** ' => [
            $this->getTableName() => $this->{$this->getTableName()},
            'sorts' => $this->sorts,
            'search' => $this->search,
            'selectedColumns' => $this->selectedColumns,
            'sortingPillsStatus' => $this->getSortingPillsStatus(),
            'sortingStatus' => $this->getSortingStatus(),
            'paginationStatus' => $this->getPaginationStatus(),
            'perPageVisibilityStatus' => $this->getPerPageVisibilityStatus(),
            'perPageAccepted' => $this->getPerPageAccepted(),
            'perPage' => $this->getPerPage(),
            'page' => $this->paginators[$this->getComputedPageName()] ?? 1,
            'searchStatus' => $this->getSearchStatus(),
            'bulkActionsStatus' => $this->getBulkActionsStatus(),
            'selected' => $this->getSelected(),
            'selectAllStatus' => $this->getSelectAllStatus(),
            'filtersStatus' => $this->getFiltersStatus(),
            'secondaryHeaderStatus' => $this->getSecondaryHeaderStatus(),
            'footerStatus' => $this->getFooterStatus(),
            'collapsingColumnsStatus' => $this->hasCollapsingColumns(),
        ]]);

and then to restore:

        if (session()->has(' THE UNIQUE KEY YOU SET BEFORE ')) {
            $save = session()->get(' THE UNIQUE KEY YOU SET BEFORE ');
            $this->{$this->getTableName()} = $save[$this->getTableName()];
            $this->sorts = $save['sorts'];
            $this->search = $save['search'];
            $this->selectedColumns = $save['selectedColumns'];
            $this->setSortingPillsStatus($save['sortingPillsStatus']);
            $this->setSortingStatus($save['sortingStatus']);
            $this->setPaginationStatus($save['paginationStatus']);
            $this->setPerPageVisibilityStatus($save['perPageVisibilityStatus']);
            $this->setPerPageAccepted($save['perPageAccepted']);
            $this->setPerPage($save['perPage']);
            $this->setPage($save['page'], $this->getComputedPageName());
            $this->setSearchStatus($save['searchStatus']);
            $this->setBulkActionsStatus($save['bulkActionsStatus']);
            $this->setSelected($save['selected']);
            $this->setSelectAllStatus($save['selectAllStatus']);
            $this->setFiltersStatus($save['filtersStatus']);
            $this->setSecondaryHeaderStatus($save['secondaryHeaderStatus']);
            $this->setFooterStatus($save['footerStatus']);
            $this->setCollapsingColumnsStatus($save['collapsingColumnsStatus']);
            session()->forget(' THE UNIQUE KEY YOU SET BEFORE ');
   }

[bLLRR]

Seeing this peace of code gives me a great starting point for a simular problem.
Just not sure wich function tracks the changes in filters, selectedColumns, ...

[lrljoe]

So in v3 we are exposing more methods for storing/retrieving table states.

I'm still looking at the various options, any ideas other than URL/Session/Cookie are welcome