Directional flow from reducer to root reducer?
I'm trying to understand the directional flow in react-redux from root reducer to reducer. I get the purpose why the store, root reducer, reducer, and action. However I'm trying to match up the snippets of code in these separate files that triggers this flow.
When the reducer return an object that has the updated states, does it go straight to the store or it gets returned to the root reducer? On diagrams and explanations it shows that it goes to root reducer, however when from what I see from the code that it is the root reducer thats calling on the reducer, therefore implying that the reducer returns an object and it gets saved to the store right away. However the bridge between the reducer and the store is the root reducer, so where is the object being dumped into right after it gets returned from the reducer?
Also, when you use mapStateToProps() in a component to get access to states does it first go the the createStore() in store, then it goes to the root reducer to gather up all the reducers, and then it return the states to the component?
Can I think of the flow as this.
Updating state:
component --> action --> reducer --> store
Retrieving state:
component --> store --> root reducer --> reducer -->
|
V
component <--store <-- root reducer <--
Thank you all.
react-redux
edited Nov 18 '18 at 19:43
Tal Avissar
5,61032344
asked Nov 18 '18 at 18:19
ThomasThomas
12
add a comment |
I'm trying to understand the directional flow in react-redux from root reducer to reducer. I get the purpose why the store, root reducer, reducer, and action. However I'm trying to match up the snippets of code in these separate files that triggers this flow.
When the reducer return an object that has the updated states, does it go straight to the store or it gets returned to the root reducer? On diagrams and explanations it shows that it goes to root reducer, however when from what I see from the code that it is the root reducer thats calling on the reducer, therefore implying that the reducer returns an object and it gets saved to the store right away. However the bridge between the reducer and the store is the root reducer, so where is the object being dumped into right after it gets returned from the reducer?
Also, when you use mapStateToProps() in a component to get access to states does it first go the the createStore() in store, then it goes to the root reducer to gather up all the reducers, and then it return the states to the component?
Can I think of the flow as this.
Updating state:
component --> action --> reducer --> store
Retrieving state:
component --> store --> root reducer --> reducer -->
|
V
component <--store <-- root reducer <--
Thank you all.
react-redux
edited Nov 18 '18 at 19:43
Tal Avissar
5,61032344
asked Nov 18 '18 at 18:19
ThomasThomas
12
Hello, I'd recommend you add the 'logger' (from redux-logger) library to your middleware when connecting to the store. It provides great logging info on the states before and after you call any action. But to answer your question, the update state is correct. I think the retrieving state is confusing. In my little knowledge it goes like this: The component connects to the store and through mapStateToProps you get the state from the reducers by calling the actions So: component -> store -> reducers -> actions -> state
– kivul
Nov 19 '18 at 14:09
add a comment |
I'm trying to understand the directional flow in react-redux from root reducer to reducer. I get the purpose why the store, root reducer, reducer, and action. However I'm trying to match up the snippets of code in these separate files that triggers this flow.
When the reducer return an object that has the updated states, does it go straight to the store or it gets returned to the root reducer? On diagrams and explanations it shows that it goes to root reducer, however when from what I see from the code that it is the root reducer thats calling on the reducer, therefore implying that the reducer returns an object and it gets saved to the store right away. However the bridge between the reducer and the store is the root reducer, so where is the object being dumped into right after it gets returned from the reducer?
Also, when you use mapStateToProps() in a component to get access to states does it first go the the createStore() in store, then it goes to the root reducer to gather up all the reducers, and then it return the states to the component?
Can I think of the flow as this.
Updating state:
component --> action --> reducer --> store
Retrieving state:
component --> store --> root reducer --> reducer -->
|
V
component <--store <-- root reducer <--
Thank you all.
react-redux
edited Nov 18 '18 at 19:43
Tal Avissar
5,61032344
asked Nov 18 '18 at 18:19
ThomasThomas
12
I'm trying to understand the directional flow in react-redux from root reducer to reducer. I get the purpose why the store, root reducer, reducer, and action. However I'm trying to match up the snippets of code in these separate files that triggers this flow.
When the reducer return an object that has the updated states, does it go straight to the store or it gets returned to the root reducer? On diagrams and explanations it shows that it goes to root reducer, however when from what I see from the code that it is the root reducer thats calling on the reducer, therefore implying that the reducer returns an object and it gets saved to the store right away. However the bridge between the reducer and the store is the root reducer, so where is the object being dumped into right after it gets returned from the reducer?
Also, when you use mapStateToProps() in a component to get access to states does it first go the the createStore() in store, then it goes to the root reducer to gather up all the reducers, and then it return the states to the component?
Can I think of the flow as this.
Updating state:
component --> action --> reducer --> store
Retrieving state:
component --> store --> root reducer --> reducer -->
|
V
component <--store <-- root reducer <--
Thank you all.
react-redux
react-redux
edited Nov 18 '18 at 19:43
Tal Avissar
5,61032344
asked Nov 18 '18 at 18:19
ThomasThomas
12
edited Nov 18 '18 at 19:43
Tal Avissar
5,61032344
asked Nov 18 '18 at 18:19
ThomasThomas
12
edited Nov 18 '18 at 19:43
Tal Avissar
5,61032344
edited Nov 18 '18 at 19:43
Tal Avissar
5,61032344
edited Nov 18 '18 at 19:43
Tal Avissar
5,61032344
5,61032344
asked Nov 18 '18 at 18:19
ThomasThomas
12
asked Nov 18 '18 at 18:19
ThomasThomas
12
asked Nov 18 '18 at 18:19
ThomasThomas
12
12
Hello, I'd recommend you add the 'logger' (from redux-logger) library to your middleware when connecting to the store. It provides great logging info on the states before and after you call any action. But to answer your question, the update state is correct. I think the retrieving state is confusing. In my little knowledge it goes like this: The component connects to the store and through mapStateToProps you get the state from the reducers by calling the actions So: component -> store -> reducers -> actions -> state
– kivul
Nov 19 '18 at 14:09
add a comment |
Hello, I'd recommend you add the 'logger' (from redux-logger) library to your middleware when connecting to the store. It provides great logging info on the states before and after you call any action. But to answer your question, the update state is correct. I think the retrieving state is confusing. In my little knowledge it goes like this: The component connects to the store and through mapStateToProps you get the state from the reducers by calling the actions So: component -> store -> reducers -> actions -> state
– kivul
Nov 19 '18 at 14:09
Hello, I'd recommend you add the 'logger' (from redux-logger) library to your middleware when connecting to the store. It provides great logging info on the states before and after you call any action. But to answer your question, the update state is correct. I think the retrieving state is confusing. In my little knowledge it goes like this: The component connects to the store and through mapStateToProps you get the state from the reducers by calling the actions So: component -> store -> reducers -> actions -> state
– kivul
Nov 19 '18 at 14:09
Hello, I'd recommend you add the 'logger' (from redux-logger) library to your middleware when connecting to the store. It provides great logging info on the states before and after you call any action. But to answer your question, the update state is correct. I think the retrieving state is confusing. In my little knowledge it goes like this: The component connects to the store and through mapStateToProps you get the state from the reducers by calling the actions So: component -> store -> reducers -> actions -> state
– kivul
Nov 19 '18 at 14:09
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53364093%2fdirectional-flow-from-reducer-to-root-reducer%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53364093%2fdirectional-flow-from-reducer-to-root-reducer%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Hello, I'd recommend you add the 'logger' (from redux-logger) library to your middleware when connecting to the store. It provides great logging info on the states before and after you call any action. But to answer your question, the update state is correct. I think the retrieving state is confusing. In my little knowledge it goes like this: The component connects to the store and through mapStateToProps you get the state from the reducers by calling the actions So: component -> store -> reducers -> actions -> state
– kivul
Nov 19 '18 at 14:09