Skip to content
Redux + rxjs + redux-obersvable best practice
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.vscode
docs
examples
packages/core
.coveralls.yml
.editorconfig
.gitignore
.travis.yml
README.md
TODO.md
lerna.json
logo.png
mocha.opts
package-lock.json
package.json
tsconfig.json
tslint.json

README.md

Reobservable

Redux + rxjs + redux-obersvable best practice. Inspired by dva, rematch.

https://reobservable.github.io/reobservable/


Coverage Status Build Status

Motivation

I'm a big fan of dvajs, it helps me get rid out of the boilerplate of redux. But I think redux-saga in dva sometimes can be a little bit verbose since I prefer functional reactive programming(frp) than imperative programming.

I know that reinvent the weel could be a terrible practice, but in dva community, there is no plan to support frp. At last, I decided to create reobservable, which, in a world, is a state manager mixined dva architecture and frp features(RxJS + redux-observable. In reobservable, dva architecture wiped out the boilerplate code of redux, RxJS played an elite role in managing asynchronous task.

If you:

  • love redux concept, love the predicatable, centralized, debuggable features
  • stuking with the boilerplate code of redux
  • want to use RxJS to managing asynchronous task

try reobservable!

Installation

npm install @reobservable/core --save

Examples

See reobservble examples

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.