Composing Nested Reducers on Same Level
I would like to have the following redux state managed by a Person
reducer and an Address
reducer:
{
person: {
name: 'John Doe',
address: {
street: '123 Main Street',
...
}
}
I've tried using combineReducer
and reduceReducer
, but I'm not able to get the desired outcome.
Ideally, the person reducer manages the properties directly under it while address does the same.
What am I missing?
reactjs redux
add a comment |
I would like to have the following redux state managed by a Person
reducer and an Address
reducer:
{
person: {
name: 'John Doe',
address: {
street: '123 Main Street',
...
}
}
I've tried using combineReducer
and reduceReducer
, but I'm not able to get the desired outcome.
Ideally, the person reducer manages the properties directly under it while address does the same.
What am I missing?
reactjs redux
What have you got so far? Please share your code. BTW, You will find it easier if you flatten your state, so you will have a persons section of state and an addresses section, linked by ids.
– dashton
Dec 31 '18 at 17:31
add a comment |
I would like to have the following redux state managed by a Person
reducer and an Address
reducer:
{
person: {
name: 'John Doe',
address: {
street: '123 Main Street',
...
}
}
I've tried using combineReducer
and reduceReducer
, but I'm not able to get the desired outcome.
Ideally, the person reducer manages the properties directly under it while address does the same.
What am I missing?
reactjs redux
I would like to have the following redux state managed by a Person
reducer and an Address
reducer:
{
person: {
name: 'John Doe',
address: {
street: '123 Main Street',
...
}
}
I've tried using combineReducer
and reduceReducer
, but I'm not able to get the desired outcome.
Ideally, the person reducer manages the properties directly under it while address does the same.
What am I missing?
reactjs redux
reactjs redux
asked Dec 31 '18 at 16:57
Tyler MurryTyler Murry
97411130
97411130
What have you got so far? Please share your code. BTW, You will find it easier if you flatten your state, so you will have a persons section of state and an addresses section, linked by ids.
– dashton
Dec 31 '18 at 17:31
add a comment |
What have you got so far? Please share your code. BTW, You will find it easier if you flatten your state, so you will have a persons section of state and an addresses section, linked by ids.
– dashton
Dec 31 '18 at 17:31
What have you got so far? Please share your code. BTW, You will find it easier if you flatten your state, so you will have a persons section of state and an addresses section, linked by ids.
– dashton
Dec 31 '18 at 17:31
What have you got so far? Please share your code. BTW, You will find it easier if you flatten your state, so you will have a persons section of state and an addresses section, linked by ids.
– dashton
Dec 31 '18 at 17:31
add a comment |
1 Answer
1
active
oldest
votes
Sounds like you're looking for relationship between 2 reducers. You can consider normalizing the state shape.
Normalized Person
reducer could look like:
{
persons: {
byId: {
person1: {
id: 'person1',
name: 'John Doe',
address: 'address1'
}
}
}
}
While the Address
becomes:
{
addresses: {
byId: {
address1: {
id: 'address1',
street: '123 Main Street',
// ....
}
}
}
}
add a comment |
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%2f53989716%2fcomposing-nested-reducers-on-same-level%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sounds like you're looking for relationship between 2 reducers. You can consider normalizing the state shape.
Normalized Person
reducer could look like:
{
persons: {
byId: {
person1: {
id: 'person1',
name: 'John Doe',
address: 'address1'
}
}
}
}
While the Address
becomes:
{
addresses: {
byId: {
address1: {
id: 'address1',
street: '123 Main Street',
// ....
}
}
}
}
add a comment |
Sounds like you're looking for relationship between 2 reducers. You can consider normalizing the state shape.
Normalized Person
reducer could look like:
{
persons: {
byId: {
person1: {
id: 'person1',
name: 'John Doe',
address: 'address1'
}
}
}
}
While the Address
becomes:
{
addresses: {
byId: {
address1: {
id: 'address1',
street: '123 Main Street',
// ....
}
}
}
}
add a comment |
Sounds like you're looking for relationship between 2 reducers. You can consider normalizing the state shape.
Normalized Person
reducer could look like:
{
persons: {
byId: {
person1: {
id: 'person1',
name: 'John Doe',
address: 'address1'
}
}
}
}
While the Address
becomes:
{
addresses: {
byId: {
address1: {
id: 'address1',
street: '123 Main Street',
// ....
}
}
}
}
Sounds like you're looking for relationship between 2 reducers. You can consider normalizing the state shape.
Normalized Person
reducer could look like:
{
persons: {
byId: {
person1: {
id: 'person1',
name: 'John Doe',
address: 'address1'
}
}
}
}
While the Address
becomes:
{
addresses: {
byId: {
address1: {
id: 'address1',
street: '123 Main Street',
// ....
}
}
}
}
answered Dec 31 '18 at 18:19
Liren YeoLiren Yeo
1,1151519
1,1151519
add a comment |
add a comment |
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%2f53989716%2fcomposing-nested-reducers-on-same-level%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
What have you got so far? Please share your code. BTW, You will find it easier if you flatten your state, so you will have a persons section of state and an addresses section, linked by ids.
– dashton
Dec 31 '18 at 17:31