Giter VIP home page Giter VIP logo

redux-rx's Introduction

redux-rx

build status npm version

RxJS utilities for Redux. Includes

  • A utility to create Connector-like smart components using RxJS sequences.
    • A special version of bindActionCreators() that works with sequences.
  • An FSA-compliant observable middleware
  • A utility to create a sequence of states from a Redux store.
npm install --save redux-rx rx

Usage

import { createConnector } from 'redux-rx/react';
import { bindActionCreators, observableMiddleware, observableFromStore } from 'redux-rx';

createConnector(selectState, ?render)

This lets you create Connector-like smart components using RxJS sequences. selectState() accepts three sequences as parameters

  • props$ - A sequence of props passed from the owner
  • state$ - A sequence of state from the Redux store
  • dispatch$ - A sequence representing the dispatch() method. In real-world usage, this sequence only has a single value, but it's provided as a sequence for correctness.

selectState() should return a sequence of props that can be passed to the child. This provides a great integration point for sideways data-loading.

Here's a simple example using web sockets:

const TodoConnector = createConnector((props$, state$, dispatch$) => {
  // Special version of bindActionCreators that works with sequences; see below
  const actionCreators$ = bindActionCreators(actionCreators, dispatch$);
  const selectedState$ = state$.map(s => s.messages);

  // Connect to a websocket using rx-dom
  const $ws = fromWebSocket('ws://chat.foobar.org').map(e => e.data)
    .withLatestFrom(actionCreators$, (message, ac) =>
      () => ac.receiveMessage(message)
    )
    .do(dispatchAction => dispatchAction()); // Dispatch action for new messages

  return combineLatest(
    props$, selectedState$, actionCreators$, $ws,
    (props, selectedState, actionCreators) => ({
      ...props,
      ...selectedState,
      ...actionCreators
    }));
});

Pretty simple, right? Notice how there are no event handlers to clean up, no componentWillReceiveProps(), no setState. Everything is just a sequence.

If you're new to RxJS, this may look confusing at first, but — like React — if you give it a try you may be surprised by how simple and fun reactive programming can be.

TODO: React Router example. See this comment for now.

render() is an optional second parameter which maps child props to a React element (vdom). This parameter can also be a React Component class — or, if you omit it entirely, a higher-order component is returned. See createRxComponent() of react-rx-component for more details. (This function is a wrapper around that library's createRxComponent().)

Not that unlike Redux's built-in Connector, the resulting component does not have a select prop. It is superseded by the selectState function described above. Internally, shouldComponentUpdate() is still used for performance.

NOTE createConnector() is a wrapper around react-rx-component. Check out that project for more information on how to use RxJS to construct smart components.

bindActionCreators(actionCreators, dispatch$)

This is the same, except dispatch$ can be either a dispatch function or a sequence of dispatch functions. See previous section for context.

observableMiddleware

The middleware works on RxJS observables, and Flux Standard Actions whose payloads are observables.

The default export is a middleware function. If it receives a promise, it will dispatch the resolved value of the promise. It will not dispatch anything if the promise rejects.

If it receives an Flux Standard Action whose payload is an observable, it will

  • dispatch a new FSA for each value in the sequence.
  • dispatch an FSA on error.

The middleware does not subscribe to the passed observable. Rather, it returns the observable to the caller, which is responsible for creating a subscription. Dispatches occur as a side effect (implemented using doOnNext() and doOnError()).

Example

// fromEvent() used just for illustration. More likely, if you're using React,
// you should use something rx-react's FuncSubject
// https://github.com/fdecampredon/rx-react#funcsubject
const buttonClickStream = Observable.fromEvent(button, 'click');

// Stream of new todos, with debouncing
const newTodoStream = buttonClickStream
  .debounce(100)
  .map(getTodoTextFromInput);

// Dispatch new todos whenever they're created
dispatch(newTodoStream).subscribe();

observableFromStore(store)

Creates an observable sequence of states from a Redux store.

This is a great way to react to state changes outside of the React render cycle. See this discussion for an example. I'll update with a proper example once React Router 1.0 is released.

Also, I'm not a Cycle.js user, but I imagine this is useful for integrating Redux with that library.

redux-rx's People

Contributors

acdlite avatar cesarandreu avatar chicoxyzzy avatar chrisvfritz avatar ferdinandsalis avatar frederickfogerty avatar iamdmhero avatar jjt avatar matthewwithanm avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

redux-rx's Issues

Allow more maintainers

@acdlite

I greatly appreciate what you've done to get this started and I'm sure it came out of a passion for using RxJs with Redux/React for yourself. However, there are several simple clean up tasks that are going by the wayside due to how busy you are and it's preventing those interested from adopting a truly Reactive application from using your great and simple library.

My one request is that you open this up to maintenance by more people so that the following items can get done:

  • Publish the latest version with the fix for the Redux Middleware API to NPM
    • somehow npm install redux-rx installs version 0.5.0 but the latest Release for the repo is tagged as 0.4.0, neither of which have the fix for the Middleware API
  • close several issues which have been resolved
  • Improve the examples that are provided by including import statements at the top and an example of how to use it with react-redux, specifically:
    • finish the createConnector example by showing how it is used with the Todo component
    • personally an example of passing props down from parent containers to child components, e.g. what does the binding statement look like?
  • Provide examples of the other parts of the API, e.g. the current example for observableMiddleware doesn't even include observableMiddleware in the example
  • Make rx and redux peer dependencies
  • Update react-component-rx dependency => rx-recompose
    • OR should we be using that completely instead of this package?
  • Document what other packages are necessary ( rx-react ?) or useful ( recompose - another one of yours ) in order to understand the examples or make it easier to use this library
  • Have an ability not to use FSA compliant actions - this appears to be an arbitrary dependency but I could be wrong

Personally, I'd be more than happy to perform these activities but at the moment I'm struggling with learning how to use this with my own new implementation of React+Redux Universal so I certainly can't provide help with examples

Thanks again!

Roadmap for Future Development

From a comment by @chicoxyzzy in #18 - a chance for those actively using this library to weigh in on what gets done next.

My thoughts are (reprinted/modified from #18):

  • Publish the latest version with the fix for the Redux Middleware API to NPM
    • somehow npm install redux-rx installs version 0.5.0 but the latest Release for the repo is tagged as 0.4.0, neither of which have the fix for the Middleware API
  • close several issues which have been resolved
  • Improve the examples that are provided by including import statements at the top and an example of how to use it with react-redux, specifically:
    • finish the createConnector example by showing how it is used with the Todo component
    • personally an example of passing props down from parent containers to child components, e.g. what does the binding statement look like?
  • Provide examples of the other parts of the API, e.g. the current example for observableMiddleware doesn't even include observableMiddleware in the example
  • Make rx and redux peer dependencies
  • Update react-component-rx dependency => rx-recompose
    • OR should we be using that completely instead of this package?
  • Document what other packages are necessary ( rx-react ?) or useful ( recompose - another one of yours ) in order to understand the examples or make it easier to use this library
  • Have an ability not to use FSA compliant actions - this appears to be an arbitrary dependency but I could be wrong

Not necessarily in that order.

Also some comments from @acdlite in that issue thread that modify the list above:

In addition to the sensible steps you've listed like pushing the changes to the middleware API, my suggestion is that createConnector() should be removed in favor of using rx-recompose (or similar) directly. That project + observableFromStore() + .flatMap() gives you all the power you need, and would allow the library to be view framework agnostic.

In response to my example which is

import Redux from 'redux';
import { Observable } from 'rx';
import { observableFromStore } from 'redux-rx';
import { observeProps } from 'rx-recompose';

const storeState$ = observableFromStore(store);
const fooState$ = storeState$.map(state => state.fooKey).distinctUntilChanged(fstate => fstate.id);
const FooCtor = observeProps(props$ => {
    return Observable.combineLatest(props$, fooState$, (props, fooState) => Object.assign(props, fooState);
});

const Foo = FooCtor(<div></div>);
  • I'm not sure where to use .flatMap(…) above and could use some assistance on that
  • I'm not sure if I'm implementing it right using Object.assign(…)

he also wrote

Yeah, if you do it like that you don't need .flatMap(). I was thinking about a situation like this, where you grab the store from the stream of props:

const enhance = compose(
  getContext({ store: PropTypes.object }),
  observeProps(props$ => {
    const storeState$ = props$.flatMap(props => observableFromStore(props.store))
    // ...
  })
)

observableFromStore() already supports disposal because the function passed to Observable.create() returns an unsubscribe function. Admittedly, this isn't exactly clear from the source, but here's the longer version:

export default function observableFromStore(store) {
  return Observable.create(observer => {
    const unsubscribe = store.subscribe(() => observer.onNext(store.getState()));
    // By returning unsubscribe, the observable can be disposed
    return unsubscribe;
  });
}

Is there anything else you'd like to see?
What's immediately needed for your project?
What do you want longer term?

deprecated and unused dependencies?

using react-rx-component which is deprecated?

also requires react-redux which is not used except during tests, so it should be moved to devdependencies?

Update to [email protected]

I would really like to use this with the current version of redux.
Right now it's limited to [email protected]. Do you expect breaking
changes or might this just be done with changing the version
requirement in package.json. I might try my luck but don't have
any experience with testing this kind of thing.

Any plans for creating typescript definitions? Also, is rxjs5 on the roadmap?

Are there any types available for redux-rx? I tried npm install @types/redux-rx and looks like there are none. Eventually I tried the following:

tsconfig.json

"typeRoots": [
    "./node_modules/@types",
    "./public/shared/types"
]

index.d.ts

declare module 'redux-rx';

Eventually i got this error. After some digging on the web I understand that rx is v4 and rxjs is v5

ERROR in ./node_modules/redux-rx/lib/observableFromStore.js
Module not found: Error: Can't resolve 'rx' in '....\node_modules\redux-rx\lib'
 @ ./node_modules/redux-rx/lib/observableFromStore.js 6:10-23
 @ ./node_modules/redux-rx/lib/index.js
 @ ./public/main.ts
 @ multi (webpack)-dev-server/client?http://localhost:8081 ./public/main.ts

Considering that all I need is the following, I'll just write it myself in a service.

function observableFromStore(store) {
  return _rx.Observable.create(function (observer) {
    return store.subscribe(function () {
      return observer.onNext(store.getState());
    });
  });
}

Updated

function observableFromStore(store: Store<AppState>) {
    return Observable.create((observer: any) => {
        return store.subscribe(() => {
            return observer.next(store.getState());
        });
    });
}

Hot-Reload?

Hot reloading doesn't seem to work. Any ideas on how to get it working? What's missing?

rx and redux should be dependencies, not devDependencies

  • mkdir myProject; cd myProject (completely fresh project)
  • npm init (and hit enter a bunch of times)
  • npm i --save redux-rx
  • node -e "require('redux-rx')"
    • received: Error: Cannot find module 'rx'
  • npm i --save rx
  • node -e "require('redux-rx')"
    • received: Error: Cannot find module 'redux'
  • npm i --save redux
  • node -e "require('redux-rx')"
    • Success!

observableMiddleware usage?

The observableMiddleware accepts a next function, but redux's applyMiddleware expects a function like that accepts {dispatch: Function, getState: Function} and returns a function like redux-rx's observableMiddleware.

Are users expected to wrap observableMiddleware themselves (e.g. const realMiddleware = () => observableMiddleware;)?

Any documentation about its usage would be appreciated.

Thanks!

Need examle

Hello @acdlite,

I think that will be better if will be a simple example with Redux and Rx together. Could you please provide that?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.