Simpler API

[jxnblk]

Rewrite to consolidate the two HOCs into a single HOC. If the component does not have a parent refunk context, it becomes the provider, and if there is a a parent context, it connects to state.

Note: this is a major breaking change

// example
import connect from 'refunk'
const App = props => <div />

// create a refunk state provider
export default connect(App)

import connect from 'refunk'
const TodoList = props => <div />

// connect to the parent refunk state
export default connect(TodoList)

// initialize state with props
<App todos={[]}>
  <TodoList />
</App>

• Add channel prop support for namespacing refunk context

[nelix]

This is kind of genius, the arguments connect accepts might be a little unforgiving to future features (and I think most decorators return a closure?).
connect({namespace: 'myLib', keys: ['someKey']})(MyApp) might be better... You could then also add an option to extend/replace/mask its parent (I often nest ThemeProviders, people might wanna use this in libs).

[jxnblk]

@nelix Yeah, I want to get rid of the first arguments part and make React props the primary API for configuring the components. This also makes alternative APIs like #5 possible. For the namespace option that's sort of what I'm intending to add where I mention the channel prop, i.e. a way to have multiple refunk provider instances in a single app without colliding