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

Remember Filter on Associations #3521

Open
johnvtroy opened this issue Dec 12, 2024 · 3 comments
Open

Remember Filter on Associations #3521

johnvtroy opened this issue Dec 12, 2024 · 3 comments

Comments

@johnvtroy
Copy link

Feature

Remember the Filter on has many associations when you click on Go Back after opening the record

Current workarounds

Don't use filtering on associations

Screenshots or screen recordings

12.12.2024_12.47.57_REC.mp4

Additional context

Discuss the benefit of adding this feature to associations
Related to #3497

@Paul-Bob
Copy link
Contributor

handling associations like this isn't straightforward. Each association is wrapped in a Turbo frame with a src attribute. To preserve the context for all associations when navigating back using the go back button, we'd need to maintain somewhere the state of all the params for each association and pass they to the src.

Originally posted by @Paul-Bob in #3502 (comment)

Let's figure out if there is a way of supporting this

@Paul-Bob Paul-Bob moved this to Triage in Issues Dec 12, 2024
@Paul-Bob
Copy link
Contributor

There is a cache_resource_filters configuration that enables persistent filters (basic filters).

To address this issue, we can extend cache_resource_filters to apply to dynamic filters as well and store them under a different session key when the configuration is set to true.

@adrianthedev
Copy link
Collaborator

Let's think beyond filters.
What else are we caching? Pagination?
What else could we cache, or will we in the future?

Can we come up with a better name & concept?

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

No branches or pull requests

3 participants