Closed
Description
We were able to add a lot of FAQ updates over in #1785 , but there's still some more updates I'd like added. Here's the current list of items I'd like in there:
Waiting to be Added
New topics
General
- When should I learn Redux?
- What are pros and cons of using Redux?
- How does Redux compare to [Backbone, Angular, MobX]?
- Redux vs a global variable
- How is Redux different from React's context API? Does context replace Redux?
Code Structure
- Reusable / encapsulated logic/modules?
- https://github.com/markerikson/redux-ecosystem-links/blob/master/component-state.md
- https://github.com/markerikson/react-redux-links/blob/master/redux-techniques.md#encapsulation-and-reusability
- http://randycoulman.com/blog/
- https://github.com/slorber/scalable-frontend-with-elm-or-redux
- http://www.webpackbin.com/VkHniHP6b
- Where should websockets and other persistent connections live?
- In middleware. See existing examples at https://github.com/markerikson/redux-ecosystem-links/blob/master/middleware-sockets-adapters.md
Actions
- Should I use thunks, sagas, or something else?
Performance
- Pagination/caching?
- http://stackoverflow.com/questions/33940015/how-to-choose-the-redux-state-shape-for-an-app-with-list-detail-views-and-pagina
- Cache API: invalidation, expiration, refresh, clean, TTL, LRU... facebook/relay#720 (comment)
- https://twitter.com/acemarke/status/804071531844423683
- https://medium.com/@dcousineau/advanced-redux-entity-normalization-f5f1fe2aefc5
- Related to existing "state tree size" question
Design Decisions
- Why does Redux separate out actions and updates? Why not just update state directly?
React-Redux
- Why use React-Redux?
Other
- Fit these diagrams in somewhere? Docs need one or more diagrams #653
- "FAQ-worthy" mentions:
- Boilerplate/verbosity:
Updates to Existing Questions
- When should I use Redux?
- Where should I put "business logic" ?
It's not an FAQ item, but I'll leave a note for myself here rather than filing a new issue. The "Beyond combineReducers" page should have a mention of "double-nesting state", as in state.posts.posts
, usually due to initial state defining a key and the slice reducer being given a key. . Definitely a common mistake.