Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/694590c5-f52c-800f-9af6-d10143a2d812
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== Assistant: Short answer: yes — every dispatched action is broadcast to the whole store, and any slice that has a case matching tha… === Short answer: yes — every dispatched action is broadcast to the whole store, and any slice that has a case matching that action will run its reducer for it. There’s no implicit one-way restriction. Key points: * dispatch(userLoggedOut()) sends an action { type: 'auth/userLoggedOut', ... } to the store. - The auth slice reducer (if it defines that case) will run. - Any other slice that called builder.addCase(userLoggedOut, ...) will also run its case reducer (e.g., postsSlice clearing posts). * dispatch(postUpdated(...)) behaves the same: all reducers see the action; only slices that declared a case for that action will change state. Important distinctions: * Actions are just plain objects with a type. Reducers decide whether to react. Nothing “calls functions in other slices” automatically except the reducers that explicitly handle that action. * If you want multiple things to happen as part of a logical operation, either: - dispatch a single shared action (and have other slices handle it via extraReducers), or - dispatch multiple actions from a thunk: dispatch(doA()); dispatch(doB()); * Middleware/listeners (thunks, createListenerMiddleware) can run extra side effects when actions are dispatched. * Don’t dispatch inside reducers. Use middleware/thunks for side effects or chained dispatches. Example: <syntaxhighlight lang="ts">// authSlice exports userLoggedOut builder.addCase(userLoggedOut, state => { /'' auth cleanup ''/ }) // postsSlice builder.addCase(userLoggedOut, () => initialPostsState) // reacts to logout // but postsSlice won't react to postUpdated unless it explicitly handles it </syntaxhighlight>
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)