Skip to content
This repository was archived by the owner on Jun 6, 2019. It is now read-only.

Conversation

@wallzero
Copy link

Based on the following issue: #4

@wallzero
Copy link
Author

Nevermind this still doesn't work. If the scan returns that state it also overwrites any states called by nested reducers.

@wallzero
Copy link
Author

wallzero commented Feb 23, 2017

Tried using an || instead of storing the object but seems to only work some of the time; I'm guessing it depends on the order of the reducers in the scan. It be great if there was a way to have the scan itself skip returning an item.

Remove handling of undefined returns from reducer
@wallzero
Copy link
Author

In the end I don't think this PR is going to resolve my issue. I think handling undefined is a good practice, but it seems if I don't return (state) > state, the scan will overwrite any changes to state by nested reducers. I've removed the undefined handler and now this PR is only about scoped imports. I'll continue comments in the issue ticket.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants