Skip to content

Fix state after returning new state object from reduce.#645

Open
JorgenEvens wants to merge 3 commits intogoatslacker:masterfrom
JorgenEvens:bug/model-state-unaffected
Open

Fix state after returning new state object from reduce.#645
JorgenEvens wants to merge 3 commits intogoatslacker:masterfrom
JorgenEvens:bug/model-state-unaffected

Conversation

@JorgenEvens
Copy link
Copy Markdown

After returning a new state object from a reduce method there are now two state objects being used by the store. The one stored on model.state and the one stored on the AltStore instance.

The easiest way to see this is by checking whether the state passed into the reduce method is the same as that available onthis ( the model as reduce is called on it ). I would expect it to be, but it is not.

@JorgenEvens JorgenEvens force-pushed the bug/model-state-unaffected branch from 37b8e1b to 5a1d94e Compare April 26, 2016 21:35
@JorgenEvens
Copy link
Copy Markdown
Author

I've added node 5.11 to the list of node engines to test on Travis-CI as Babel does not seem to be to happy with node v6.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant