reducer | Friendly professional-level data reduction

I just integrated to redux-toolkit . My goal is to store the result of the query getPosts in a slice, so I can use it across the site or change it.

My createApi is like this:

I found the state.elements was changed in console, even I do not dispatch yet. What is the reason?

I have a state with the following structure. It contains a list of Workouts and each workout has a list of exercises related to this workout. I want to be able to do 2 things:

1. add new exercises to the specific workout from the list of workouts
2. delete a specific exercise from the specific workout

E.g. In my UI I can add new exercises to Workout with the name Day 2. So my action payload gets 2 params: workout index (so I can find it later in the state) and exercise that should be added to/deleted from the list of exercises of the specific workout.

State

I’m writing a pretty complex app in React/Redux/Redux Toolkit, and I came across a situation which I’m not really sure how to handle. I found a way to do it, but I’m wondering if it can cause issues or if there is a better way. The short version is that I want the reducer to communicate to the caller without modifying the state, and the only way I’ve found is to mutate the action.

Description:

To simplify, let’s say that I want to implement a horizontal scrollbar (but in reality it’s significantly more complicated). The state contains the current position, a number capped between some min and max values, and the UI draws a rectangle that has that position and that can be clicked and dragged horizontally.

Main property: If the user clicks and drags further than the min/max value, then the rectangle does not move further, but if the user then moves in the other direction, the rectangle should wait until the mouse is back at its original position before starting to move back (exactly like scrollbars behave on most/all operating system).

Keep in mind that my real use case is significantly more complex, I have a dozen of similar situations, sometimes capping between min and max, sometimes snapping every 100 pixels, sometimes more complicated constraints that depend on various parts of the state, etc. I’d like a solution that works in all such cases and that preserves the separation between the UI and the logic.

Constraints:

• I do not want the UI/component/custom hook to have the responsibility to compute when we reach the min/max, because in my use case it can be pretty complex and depend on various parts of the state. So the reducer is the only place that knows whether we did reach the min/max.
• On the other hand, in order to implement the Main property above, I do need to somehow remember where we clicked on the rectangle, or how many pixels of a given "drag" action was handled, in order to know when to start moving back. But I don’t want to store that in the state as it’s really a UI detail that doesn’t belong there (and also because I have quite a few different situations where I need to do that and my state would become significantly more complex, and unnecessary state changes will be performance heavy).

Problem:

So the reducer is the only part that knows if we reached the min/max, and the only way a reducer usually communicates to the rest of the app is through the state, but I don’t want to communicate that information through the state.

Solution?

I actually managed to find a way to solve it, which seems to work just fine but feels somewhat wrong: mutating the action object in the reducer.

The reducer takes the action "dragged by 10 pixels", realizes that it can only drag by 3 pixels, creates a new state where it has been dragged by 3 pixels, and adds an action.response = 3 field to the action.

Then after my custom hook dispatched the "dragged by 10 pixels" action, it looks at the action.response field of the return value of dispatch to know how much was actually handled, and it remembers the difference with the expected value (in this case it remembers that we are 7 pixels away from the original position). In this way, if at the next mousemove we drag by -9 pixels, my custom hook can add that number to the 7 pixels it remembers, and tell the reducer that we only moved by -2 pixels.

It seems to me that this solution preserves separation of UI/logic perfectly:

• The reducer only needs to know by how many pixels we moved and then return the new state and how many pixels were actually handled (through mutating the action)
• The custom hook can remember how far off we are from the original position (without having to know why), and then it will simply correct event.movementX to compensate with how much the reducer didn’t handle in previous actions, and then send the correct delta to the reducer.

It also works just fine with things like snapping at every 100 pixels or such.

The only weird thing is that the reducer mutates the action, which I would assume is not supposed to happen as it should be a pure function, but I couldn’t find any issue with it so far. The app just works, Redux Toolkit doesn’t complain, and the devtools work just fine as well.

Is there any issue with this solution?

Is there another way it could be done?

I'm really new to React and need to ask. Can I have a ReactJs Redux store in a library and then use that library in an App that also has a Redux store?

Both of them do this:

RE: What is the best way to pass generic function that resolves to multiple types

Please read the referenced link before going further below

I am trying to extend the concept and pass a generic function that takes 2 parameters and does something with them.

The static approach works, however the interface based one causes a compile error (see the code lines marked with //error):

New on Reactjs, trying to learn by coding, i need some help/advice with the code, with converting this Redux store to Redux toolkit, here i'm using function called configureStore, what is good way of changing this into using the 'configureStore' which comes from '@reduxjs/toolkit' this is for learning purpose that 'createRootReducer' comes from my reducers.js which combines

App purpose: The purpose of this React app is to handle scoring of a very specific dart-game. 2 players, each having to reach 33 hits in the fields 20-13, Tpl's, Dbls's and Bulls. No points, only the number of hits are counted. The hits are added manually by the players (no automatiion required :)). Each targetfield has a row of targets and 2 buttons for adding and removing a hit of that target field.

I have implemented the useContext-design for maintaining state, which looks like this:

I have following action in redux action.js file,