Documentation for Persistence and Rehydration

[OscarMpy]

Issue Description

The documentation on state persistence and rehydration use redux-persist as a reference, and there seems to be uncertainty around the maintenance of the redux-persist repository. As highlighted in rt2zz/redux-persist#1463, there are concerns that the repo is not actively managed, which may discourage its use in production environments.

Proposal for Redux Toolkit Documentation

Given that Redux Toolkit aims to provide a standard way to write Redux logic, it could be beneficial for the community if the documentation could include:

• Updated guidance on state persistence and rehydration, possibly with maintained alternatives to redux-persist.
• An assessment or recommendation about the viability of transitioning to alternatives like redux-remember, which was suggested by @wmonecke in the aforementioned issue.

Questions

1. Are there any plans to update the Redux Toolkit documentation to reflect more current or actively maintained persistence solutions?
2. Can the Redux Toolkit team provide insights or endorsements for libraries that might serve as suitable replacements for redux-persist?

Please don't misunderstand me, redux-persist works exceptionally well and has established a solid foundation; my concerns are on its reliability as a long-term solution.

[markerikson]

We try to limit the RTK docs to just material about the library itself (usage and API reference).

It might make sense to have a usage guide on persistence in the core docs, as the concepts apply whether you're using the original redux core library or RTK.

None of us maintainers actively use persistence ourselves, so our knowledge is limited here. That said, https://github.com/zewish/redux-remember seems like it's a more recent alternative to redux-persist (and I see you've seen that).