Skip to content
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

admin-ui: Order List Custom filter persistence #561

Closed
chladog opened this issue Nov 18, 2020 · 2 comments
Closed

admin-ui: Order List Custom filter persistence #561

chladog opened this issue Nov 18, 2020 · 2 comments

Comments

@chladog
Copy link
Contributor

chladog commented Nov 18, 2020

Is your feature request related to a problem? Please describe.
Now users can set up quite complex filters by themselves. It's tedious for them to set the filters they need to use on daily basis on every refresh/navigation to the Custom Filters.

Describe the solution you'd like

  • store current filter settings as URL query parameter and load the filters from it on navigation
  • additionally store latest settings in users persistence either in DB or localStorage (Personally would lean towards localStorage) and load these (to URL query & filter settings) when toggling/navigating to Custom Filters view.

With implementation of both of these features, users would be able:

  • save their favorite filter settings as a bookmark
  • share their filters with other users
  • keep last set filter when navigating out of Custom Filters view
  • keep last set filter when reloading the application
@michaelbromley
Copy link
Member

I agree with all of the above.

Related: I've been thinking of adding a new field to the Administrator type which allows storage of arbitrary UI settings. This would allow e.g. filter settings to be persisted to the backend, meaning they are available even when logging in on another device. The motivation for this concept was being able to customize what widgets to display on the dashboard. But it also would fit this issue nicely as well.

@chladog
Copy link
Contributor Author

chladog commented Nov 18, 2020

As these settings will be stored as stringified JSONs probably then compability with coming features in future releases and merging the settings without loosing the existing settings should be considered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants