Our great sponsors
-
Honestly, before Redux Toolkit and Redux RTK Query, there were a lot of pain points with Redux.
-
For storage layer issues specifically, I'll direct you to redux-persist. It's been a perfect solution for almost all of my persisting needs over the years.
-
Appwrite
Appwrite - The Open Source Firebase alternative introduces iOS support . Appwrite is an open source backend server that helps you build native iOS applications much faster with realtime APIs for authentication, databases, files storage, cloud functions and much more!
-
As for undoing, my personal opinion is that it is never required. After all, undoing an action is really just dispatching a new action with the information to repopulate which you can compute on the fly. An added benefit of this method is your action history is always moving forward, never backwards. That being said, this redux-undo library might help. Note, I have never used it, but it does come back to my point that middleware are usually the solution.
-
FWIW, there are some various other third-party replacements for combineReducers that might be useful (see https://github.com/markerikson/redux-ecosystem-links/blob/master/reducers.md ), but you'd have to specifically choose to use them yourself, and on top of that createSlice wouldn't be expecting a third arg or pass it through to its case reducers.
-
We've completely revamped the Reselect types in the last few weeks and added new cache size options to its API - see https://github.com/reduxjs/reselect/releases
