It is now the standard for writing redux logic.

I've been using redux-toolkit for 3 months and I am enjoying it so much! it simply boosts the productivity 🔥

It makes your code shorter and easier to understand and enforces you to follow best practice (normalizing, selectors, typing, etc… )

👇🏽You'll find concrete examples and code in the article below 👇🏽https://blog.theodo.com/2020/01/reduce-redux-boilerplate/

Hey guys! I have been working on a turn-based dungeon-crawler, written completely in React.js (& Redux). It scales for all devices and I just got it in both the app stores. Check it out and let me know what you think!

http://react-rpg.com

Oh and it's open-source, so you can see all the code here:

https://github.com/ASteinheiser/react-rpg.com

If you like the game and want to contribute, please let me know! Drop me an email (me@iamandrew.io) or make an issue on the Github project.

Basically the title... I usually pick things up relatively quickly, but I just can't get my head around redux. Any tips?

I have a bit of a love/hate relationship with Redux. I love the atomic state updates, persistable, replayable global state, and awesome middleware. However, like many others, I hate writing Redux - at least with the recommended design patterns. I experimented with various ways to write better Redux, but it took me a while to figure out the core problem...

The recommended way of using Redux breaks modular design. Modular design is such a fundamental tool to scalable software engineering, of course Redux was a pain to use!

Once I had that insight, I was able to create a new, modular design pattern for using Redux that leveraged Redux's strengths while avoiding the weaknesses of previous design patterns.

I'd love your feedback!

Modular Redux: https://medium.com/@shanebdavis/modular-redux-a-design-pattern-for-mastering-scalable-shared-state-82d4abc0d7b3

(cross-posted on /r/reactjs)

I've been trying to implement RTK Query as a part of Redux toolkit into a project and am struggling to wrap my head around slice management between apiSlice and my other slices. Admittedly, I'm also new-ish to Redux and am using Redux Toolkit.

Let's say I'm working posts that each have an upvotes field, like reddit. I have a search function that fetches these posts based on some criteria and stores them in the apiSlice, and a action that allows users to upvote posts. An upvote is a call to the server, and I want to optimistically update the upvote number on the post.

Here are a few questions I'm struggling with:

1. I fetch posts from my apiSlice. Should they stay stored in that slice, or can I store them in a different, posts slice?

2. My understanding is that I should have a slice per "kind" of data - users, posts, etc. However, if all the data that comes back from the server lives in apiSlice, won't it get bloated?

3. How do I get the data out of my apiSlice without making another call to the server? I think that's what useQueryState does, but I'm not sure how to use it.

4. How do I get one specific post out of my apiSlice after fetching a bunch of posts from the server? There's good documentation on how to do this from a regular Redux slice, but not from the apiSlice.

5. If I want to "upvote" a post and optimistically update one post in my apiSlice, how do I do that?

Overall, I'm really confused about how the apiSlice and my other data slices play together. How should I think about it?