Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Updating nested data in redux store

What's the best/correct way to update a nested array of data in a store using redux?

My store looks like this:

{     items:{         1: {             id: 1,             key: "value",             links: [                 {                     id: 10001                     data: "some more stuff"                 },                 ...             ]         },         ...     } } 

I have a pair of asynchronous actions that updates the complete items object but I have another pair of actions that I want to update a specific links array.

My reducer currently looks like this but I'm not sure if this is the correct approach:

  switch (action.type) {     case RESOURCE_TYPE_LINK_ADD_SUCCESS:       // TODO: check whether the following is acceptable or should we create a new one?       state.items[action.resourceTypeId].isSourceOf.push(action.resourceTypeLink);       return Object.assign({}, state, {         items: state.items,       });   } 
like image 327
Clarkie Avatar asked Aug 21 '15 08:08

Clarkie


People also ask

How do we update the Redux store?

First we find the index of the item in the State array by using findIndex. In the picture above, x+1 is the index of the item needs updating. Once the updated object is created, the quickest way to update is using the slice method and spread operator (…).

How do you handle nested objects in react?

If we want to access all the values of nested objects then we have to use recursion to access each and every level of that object. And it can get more complicated according to the nesting of the object. That why we have to use recursion to get all the values and access the whole nested object.


2 Answers

Jonny's answer is correct (never mutate the state given to you!) but I wanted to add another point to it. If all your objects have IDs, it's generally a bad idea to keep the state shape nested.

This:

{   items: {     1: {       id: 1,       links: [{         id: 10001       }]     }   } } 

is a shape that is hard to update.

It doesn't have to be this way! You can instead store it like this:

{   items: {     1: {       id: 1,       links: [10001]     }   },   links: {     10001: {       id: 10001     }   } } 

This is much easier for update because there is just one canonical copy of any entity. If you need to let user “edit a link”, there is just one place where it needs to be updated—and it's completely independent of items or anything other referring to links.

To get your API responses into such a shape, you can use normalizr. Once your entities inside the server actions are normalized, you can write a simple reducer that merges them into the current state:

import merge from 'lodash/object/merge';  function entities(state = { items: {}, links: {} }, action) {   if (action.response && action.response.entities) {     return merge({}, state, action.response.entities);   }    return state; } 

Please see Redux real-world example for a demo of such approach.

like image 115
Dan Abramov Avatar answered Oct 06 '22 00:10

Dan Abramov


React's update() immutability helper is a convenient way to create an updated version of a plain old JavaScript object without mutating it.

You give it the source object to be updated and an object describing paths to the pieces which need to be updated and changes that need to be made.

e.g., if an action had id and link properties and you wanted to push the link to an array of links in an item keyed with the id:

var update = require('react/lib/update')  // ...  return update(state, {   items: {     [action.id]: {       links: {$push: action.link}     }   } }) 

(Example uses an ES6 computed property name for action.id)

like image 42
Jonny Buchanan Avatar answered Oct 06 '22 00:10

Jonny Buchanan