Does state changing is async? about redux-actions

[simondell]

I don't have a whole answer for you, only one part.

Your reducer is mutating some of the state, instead of recreating it all. You have this line:

updatedWinnings.claimed[indexOfWinningInClaimed].isPending = false

... which changes the value of isPending on one item from a collection. However, you are not then making a new item with the new property value; you are returning the same item with the value mutated. Also, you are not returning a new .claimed array; only the same array with one property of one member changed. Because of this, the store->selectors->connect()->props->shouldComponentUpdate() sections of the component lifecycle will (probably) not notice that updatedWinnings.claimed[indexOfWinningInClaimed] has changed.

You could try modifying this reducer to make a new updatedWinnings.claimed array, with a new [indexOfWinningInClaimed] item, with the new .isPending value.

My preference would be to extract more and more specialised reducers. The one you have now operates on the collection. Make a new one which operates on an item in the collection (handling any actions it may need). You might need to go deeper still if the other data in updatedWinnings.claimed[indexOfWinningInClaimed] is rich and nested.

[simondell]

(This is likely not a problem with redux-actions. You might get better answers if you ask again on StackOverflow with a [redux] tag. However, redux-actions can help you: its handleActions() function makes it much easier to create layers of reducers with pass smaller and smaller pieces of state, and the action, to one another.)

[tonoyandev]

@simondell thanks, yes that was not related to redux-actions. Closed.