Persistent form state support in TanStack Form?
Hi! 
I’m exploring TanStack Form for handling filters in my app. One thing I’ve run into is that when users navigate away from a page and then come back, the filter form resets instead of remembering the previous state.
Ideally, I’d like the form state to persist across navigations — similar to how filters stick around when you use query params in route history. That way, users can navigate around, then return to the page and still see their previously selected filters without having to re-enter them.
Is there a built-in way (or recommended pattern) in TanStack Form to achieve this? For example, syncing form state with the router/query string, or persisting it in local/session storage.
If not, would this make sense as a feature request?
Thanks!
I’m exploring TanStack Form for handling filters in my app. One thing I’ve run into is that when users navigate away from a page and then come back, the filter form resets instead of remembering the previous state.
Ideally, I’d like the form state to persist across navigations — similar to how filters stick around when you use query params in route history. That way, users can navigate around, then return to the page and still see their previously selected filters without having to re-enter them.
Is there a built-in way (or recommended pattern) in TanStack Form to achieve this? For example, syncing form state with the router/query string, or persisting it in local/session storage.
If not, would this make sense as a feature request?
Thanks!
