Porting redux ecosystem

[beyondeye]

Redux is a relatively low level library and not very useful without its ecosystem .
Porting redux is relatively easy. Porting its ecosystem is a lot more work.
The components I have ported in Reduks are:

• reselect
• Thunk and Promise middleware
• logger middleware
• started working on integration with immutable collections: integrated immutable map for using in redux state
• I am currently working on porting redux-sagas middleware

I would be happy if we could coordinate efforts in porting more parts of redux ecosystems

[AngusMorton]

I think the ecosystem should be ported in such a way that components are compatible with other implementations of the API. Given that, I think we should have some guidelines for components.

1. Components should be in standalone repositories (ie. not as part of a larger implementation repository).
2. Components should be compiles against the jvm-redux-api and not an implementation of the api.
3. Components should be named in such a way that it is obvious that they are part of the jvm-redux ecosystem. eg. jvm-redux-sagas, jvm-redux-logger.

We will need a reference implementation of the jvm-redux-api in order to provide a common dependency that Components can run tests against.