Sometimes we need to persist a search parameter as the user moves through different URL paths.
An example. You have a search interface where the results could be presented in different forms, one of which is stored in a tab, and the tab is part of the URL path.
Another example, a pagination or other filters should be persisted when you go from a table page to an item page and want to go back via a breadcrumbs button.
To do this, I suggest adding a subpath
parameter to the withSearchParamsPersist
/ searchParamsAtom.lens
options, which takes a string of the allowed subpath for the persistence parameter. If a navigation occurs to the path starting with the passed subpath - the parameters will be persisted.
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too