I've looked at literally hundreds of Redux-related libraries and addons (and listed anything that looks decently useful in my Redux addons catalog [0] ). As part of that, I've seen dozens and and dozens of libraries that promised to "reduce Redux boilerplate" - usually functions for generating reducers based on lookup tables rather than switch statements, but also other approaches as well.

redux-tiles adds a bit more abstraction that I personally like, but it does look useful and appears to maintain the overall spirit of Redux (as opposed to many other "wrappers" that wind up trying to add OOP/class layers on top, or obscure the fact that there's actions, reducers, and dispatching going on, per some of the examples I listed in my blog post "The Tao of Redux, Part 2 - Practice and Philosophy [1]).

I don't think I'd use this myself, but it seems like a reasonable approach to "reducing boilerplate" overall. As always, it's up to you the Redux user to decide how much abstraction you are comfortable with and want to use in your own application.

Thanks to the author for putting this together and posting it.

[0] https://github.com/markerikson/redux-ecosystem-links

[1] http://blog.isquaredsoftware.com/2017/05/idiomatic-redux-tao...