Skip to content
Built_redux provider for Flutter.
Branch: master
Clone or download
Latest commit 6903b31 Sep 1, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
example migrate to dart 2 Aug 22, 2018
lib missed the doc string Mar 2, 2018
test/unit migrate to dart 2 Aug 22, 2018
tool add example and store_connection widget Feb 26, 2018
.gitignore migrate to dart 2 Aug 22, 2018
.travis.yml remove alpha branch from travis Feb 26, 2018 migrate to dart 2 Aug 22, 2018 update readme to point to example file Feb 26, 2018
analysis_options.yaml add example and store_connection widget Feb 26, 2018



built_redux bindings for Flutter.

By creating a Widget that extends StoreConnector you get automatic subscribing to your redux store, and you component will only call setState when the store triggers and the values you take from the store in connect change!


counter example

todo_mvc, written by Brian Egan

Why you may need flutter_built_redux

For the same reason you would want to use redux with react.

from the flutter tutorial:

In Flutter, change notifications flow “up” the widget hierarchy by way of callbacks, while current state flows “down” to the stateless widgets that do presentation.

Following this pattern requires you to send any state or state mutator callbacks that are common between your widgets down from some common ancestor.

With larger applications this is very tedious, leads to large widget constructors, and this pattern causes flutter to rerun the build function on all widgets between the ancestor that contains the state and the widget that actually cares about it. It also means your business logic and network requests live in your widget declarations.

built_redux gives you a predicable state container that can live outside your widgets and perform logic in action middleware.

flutter_built_redux lets a widget to subscribe to the pieces of the redux state tree that it cares about. It also lets lets widgets dispatch actions to mutate the redux state tree. This means widgets can access and mutate application state without the state and state mutator callbacks being passed down from its ancestors!

You can’t perform that action at this time.