Reduction Sauce

Motivation

I have worked on large react redux projects, which all suffered from similar problems.

1. The largest problem was the reducer organization. Often reducers started with pure intentions, and were incrementally hijacked for view logic. The additions were small, just a couple Boolean variables here or there. Soon other views would begin depending on them. This is a problem because it implicitly binds views together and makes things hard to re-factor.
2. Another issue is that reducers can add a bit of boilerplate. Being the lazy programmers that we are, we have a tendency to tack on to whatever reducer was close enough to handle the view logic.

Reduction Sauce addresses both of these issues.

1. Automatically connecting a view with it's reducer removes the potential of creating dependencies.
2. Creating a unique reducer for each view removes the urge to tack on view logic into places it shouldn't be.

Inspirations

This library was heavily inspired/influenced by redux-forms