-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Actions are processed in renderer and main store with triggerAlias Middleware #283
Comments
I'm not aware of any issues with |
I don't think this is necessarily a bug. I believe the issue is that createSlice automatically creates an action for you based on the passed in reducer keys. However, to use triggerAlias middleware, you should be calling createAliasedAction. So instead of exporting the action created from createSlice, you would need to export an action created from createAliasedAction. It lessens the helpfulness of react toolkit, but it worked in my testing. |
In my redux store I recognized, that all actions which are dispatcher, are processed by the main and the renderer store.
As far as my store is pretty huge and the data which is processed by some actions needs a bit more calculation power, it is necessary that only the main store is processing these actions.
In the documation it is written, that the middleware
triggerAlias
should fix this problem, but actions are still processed in all stores.Also creating an alias action and dispatching that is not fixing the problem
I am using redux-toolkit to create the store. Is there any common issue known with that framework?
Here is my code to create stores
Example for reducer
The text was updated successfully, but these errors were encountered: