Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Latest commit

 

History

History
126 lines (89 loc) · 3.31 KB

views.md

File metadata and controls

126 lines (89 loc) · 3.31 KB

Views (or Components)

Combining to React

You bring all the flow together with the Views (or components), actually the Action generators. Use the Flux.mixins.storeListener mixin to get a component into the Flux system. All components to which you have applied the storeListener mixin will be able to access stores.

// Child components don't have to have the storeListener.

var TodoItemView = React.createClass({

  render: function (todo) {
    return <li onClick={this.handleClick}>{this.props.todo.text}</li>
  },

  handleClick: function () {
    TodoActionCreator.removeTodo(this.props.todo);
    // or, this.props.dispatcher.removeTodo(this.props.todo);
  }

});

var TodoListView = React.createClass({

  mixins: [Flux.mixins.storeListener],

  render: function () {
    var self = this;
    return <ul>
      {this.getStore('todoStore').todos.map(function (todo) {
        return <TodoItemView todo={todo}></TodoItemView>
      })}
    </ul>
  }

});

storeDidChange and storesDidChange

These methods are triggered when a store is changed, and all stores are changed. You can use these methods in your components to perform specific actions after a store changes. Please note that the Flux.mixins.storeListener will automatically update your component's state and force a render, so it is not required that you define these methods to perform routine re-renders.

var TodoListView = React.createClass({

  mixins: [Flux.mixins.storeListener],

  // when all stores are updated
  storesDidChange: function () {
    console.log("All stores are now updated.");
  },

  // when a store updates
  storeDidChange: function (storeName) {
    console.log(storeName + " store is now updated.");
  },

  render: function () {
    // ...
  }

});

watchStores

In larger applications, it may become inefficient to watch all stores for changes. The watchStores property is an array, defined on your component, containing the names of stores you want the component to watch for changes. This property is optional, and when omitted, all stores associated with the dispatcher will be watched. Store name strings should match the keys of the stores returned in the dispatchers's getStores method.

var TodoListView = React.createClass({

  mixins: [Flux.mixins.storeListener],

  // Only watch the todoStore, omitting this property will watch all stores on the dispatcher
  watchStores: ['todoStore'],
  
  ...

trigger

trigger is a method exposed by the Flux.mixins.storeListener. It is a simple way to trigger action from a component. See the Dispatcher docs for more.

getStore(storeName)

It returns the related store to the component.

...
  return <ul>
    {this.getStore('todoStore').todos.map(function (todo) {
      return <TodoItemView todo={todo}></TodoItemView>
    })}
  </ul>
...

Combining to Flight.js

Since DeLorean.Flux doesn't require React, you can use it everywhere, including Flight.js

var TodoCountUI = flight.component(function () {

  this.render = function () {
    this.$node.html(TodoListDispatcher.getStore('todoStore').todos.length);
  };

  this.after('initialize', function() {
    // You should listen changes
    TodoListDispatcher.on('change:all', this.render.bind(this));
    this.render();
  });
});