Not Flux

What is Not Flux

It's a flux library :) Implemented in angular to provide a quick flux pattern without having to worry about using emitChange everywhere

Features

• Actions and Stores
• Stores emit clones
• NO EMIT CHANGE!!
• Can have private functions/methods

Examples

Creating a store

.factory('SettingsStore', ['NotFlux', function(NotFlux) {
  return NotFlux.createStore({
    myInfo: {hello: 'world'},
    userId: 4,
    _privateData: 2,
 
    // Prefix methods or data with a _ to keep them off of what actions can bind to
    _myPrivateStuff: function() {
 
    },
 
    modifyInfo: function(id, info) {
      this.myInfo.hello = 'bill' + info
 
      // Emit events through the app!
      this.emit('myEvent', this.myInfo)
    },
 
    changeUserId: function(id) {
      this.userId = id
    }
  })
}])

Creating actions

.factory('SettingsActions', ['NotFlux', function(NotFlux) {
  return NotFlux.createActions([
    'setUserId',
    'changeInfo'
  ])
}])

Linking Actions to Stores

.factory('SettingsStore', ['NotFlux', 'SettingsActions', function(NotFlux, SettingsActions) {
  return NotFlux.createStore({
    myInfo: {hello: 'world'},
    userId: 4,
 
    init: function() {
      // We set the action to listen to the
      // changeUserId callback from the store
      SettingsActions.setUserId.listen(this.changeUserId)
 
      // We can even define multiple handlers
      SettingsActions.changeInfo.listen([this.modifyInfo, this.changeUserId])
    },
 
    modifyInfo: function(id, info) {
      this.myInfo.hello = 'bill' + info
    },
 
    changeUserId: function(id) {
      this.userId = id
    }
  })
}])

Linking up the view

// We must load up the store as well as the actions. This is
// so the store can be initialzed! You only
// need to initialize a store in one location
// though it will not effect anything doing so in multiple places
.controller('myCtrl', ['$scope', 'SettingsStore', 'SettingsActions', function($scope, SettingsStore, SettingsActions) {
 
  // Call bindTo to update the view on changes
  SettingsStore.bindTo($scope, function(data) {
    $scope.userId = data.userId
  })
 
  $scope.onClick = function() {
    // Call an action which will change the store
    SettingsActions.changeUserId(5)
  }
})

Methods

Store

Outside the definition

.bindTo($scope, cb)

This is for binding to the data of a store. To modify the datastream we can use tranformFn

.data(waitedAttrs)

This allows you to pull a clone of the data from the store. You can optionally pass it a single string or an array of strings to clone it once it's been filled but this required you to set it to null for initialization.

IE.

.factory('MyStore', function() {
  return NotFlux.createStore({
    // We must set these to null or else we can't tell when they get changed!
    myData: null,
    waiting: null,
  
    set: function() {
      this.myData = 'Hello world'
      this.waiting = {hi: 'bill'}
    }
  })
})
 
// hello.myData will contain the result
$scope.hello = MyStore.data('myData').result
 
// Sets $scope.myData and $scope.waiting to the data from the store once its resolved
MyStore.data(['myData', 'waiting']).set($scope)

Inside the definition

.init

A method to overload for initialization of the store. Used to bind actions.

init: function() {
  // Set `setUserId` to run store.changedUserId
  SettingsActions.setUserId.listen(this.changeUserId)

  // We can even define multiple handlers
  SettingsActions.changeInfo.listen([this.modifyInfo, this.changeUserId])
},

.transformFn(data)

This is so you can modify the outgoing stream from the store. IE.

NotFlux.createStore({
 
  // Data received by bindTo will have be +500
  transformFn: function(data) {
    data.userId += 500
 
    return data
  }
})

.emit(data)

Use this to emit system wide events IE.

NotFlux.createStore({
  myFn: function(data) {
    this.emit('hello', data)
  }
})
 
$scope.$on('hello', function(data) {
  console.log(data)
})

Actions

Actions.{name}.listen(handler)

Setup a listener for an action