Remember a selected filter or pagination status when navigating & modifying resources

[StanBarrows]

• Laravel Version: 6.0.*
• Nova Version: 2.3.0
• PHP Version: 7.3.*

Description

I've got a complaint from one of my customers that was having trouble with selected filters. If you select a filter, for example the per Page Filters and navigate within a resource the selected value is getting lost after each interaction. This is quite annoying if you have a few filters.

• The same is counting for pagination as well when saving the model and jumping back on the resource list. After you saved a resource there is no "back" button so you have to jump back on the left sided navigation ant the all fiter and pagination statui get are reseted.

Steps to reproduce

1. Select a per Page Filter and Switch the number of elements from 25 to 50

2. Edit an resources on the list

3. Cancel editing

4. Filter value got reseted

Paginate

The same is counting for pagination as well when saving the model and returning back on the resource list

1. Paginate through a list

2. Save the resource

3. Jump Back on the list

[davidhemphill]

We've discussed this several times, and the consensus is that this would be unexpected behavior for a system like ours. So as of now there's no plans to modify the current behavior.

[renky]

Is there a solution to reach this behaviour somehow? I don't really understand, why this would be unexpected bahaviour... For example: I filter my list for some resources, where I want to have a detailed look inside or even want to change some values at all users.... for sure, if I do this on my own, I could create an action for that, but for a one-time-change? In my case I'm talking about a user-management-system for a club and when the administrators work inside, the expected behaviour in fact would be to keep the filters?! So it's not really obvious what led to the decision - I could imagine that there is a global switch to change this behaviour.

[mortennajbjerg]

Any chance this could be reconsidered? Our customers would benefit from this too.

[eAvio]

I see this is marked as "implemented", but it still doesn't work on our installation - we are using latest version of laravel nova 3.30.

Do we need to enable this somewhere?

[crynobone]

@eAvio anything with next-series will only be available on Laravel Nova 4.