qmmr

var reduceReducers = function () {
    var reducers = [].slice.call(arguments);

    return function (previous, current) {
        return reducers.reduce(function (accu, curr) {
            return curr(accu, current);
        }, previous);
    };
};

qmmr

// INFO: ThunkMiddleware
var thunkMiddleware = function (store) {
    return function (next) {
        return function (action) {
            if (typeof action === 'function') {
                action(store.dispatch, store.getState);
            }

            return next(action);
        };

qmmr

Useful urls

• NaN talk
• React training
• JS bits

qmmr

###Redux Egghead Video Notes###

####Introduction:#### Managing state in an application is critical, and is often done haphazardly. Redux provides a state container for JavaScript applications that will help your applications behave consistently.

Redux is an evolution of the ideas presented by Facebook's Flux, avoiding the complexity found in Flux by looking to how applications are built with the Elm language.

####1st principle of Redux:#### Everything that changes in your application including the data and ui options is contained in a single object called the state tree

qmmr

JSX Spread Attributes

If you know all the properties that you want to place on a component a head of time, it is easy to use JSX:

  var component = <Component foo={x} bar={y} />;

Mutating Props is Bad, mkay

qmmr

Deprecating transferPropsTo

It's a common pattern in React to wrap a component in an abstraction. The outer component exposes a simple property to do something that might have more complex implementation details.

We used to have a helper function called transferPropsTo. We no longer support this method. Instead you're expected to use a generic object helper to merge props.

render() {
 return Component(Object.assign({}, this.props, { more: 'values' }));

qmmr

New React Element Factories and JSX

In React 0.12, we're making a core change to how React.createClass(...) and JSX works.

If you're using JSX in the typical way for all (and only) React components, then this transition will be seamless. Otherwise there are some minor breaking changes described below.

The Problem

qmmr

'use strict';

// simple express server
var express = require('express');
var app = express();
var router = express.Router();

app.use(express.static('public'));
app.get('/', function(req, res) {
    res.sendfile('./public/index.html');

qmmr

Strings

String.prototype.includes(txt, start)

It was meant to be String.prototype.contains like the Array.prototype.contains but it would break MooTools

let title = 'JS Futures in London!';
title.includes('JS') // true
title.includes('!') // true
title.includes('JS', 3) // false

qmmr

# load nvm
if [[ -f ~/.nvm/nvm.sh ]]; then
	. ~/.nvm/nvm.sh
	nvm use v0.10
else
	echo "You're missing .nvm.sh!"
fi

export PATH=/usr/local/bin:/usr/local/sbin:$HOME/.rvm/bin:$PATH