jordwalke

/**
 * ReactJS: JavaScript like you've always done it.
 * 
 * This example renders your top ten most followed friends/followers, `filter`ing
 * only your favorites, and putting a star on all verified accounts.
 * 
 * With ReactJS, any time your data changes, the UI is always brought up to date
 * automatically. If friends length changes, or followCount - it always shows what
 * `render` describes.
 */

ryanflorence

var pureRender = (Component) => {
  Object.assign(Component.prototype, {
    shouldComponentUpdate (nextProps, nextState) {
      return !shallowEqual(this.props, nextProps) ||
             !shallowEqual(this.state, nextState);
    }
  });
};

module.exports = pureRender;

partkyle

class Something
  constructor: ->
    @delegateObject = new Messager

class Messager
  testing: (int) ->
    console.log int
  woot: (bool) ->
    console.log bool
  nothing: (array) ->

jsteiner

{
  "app/assets/javascripts/models/*.coffee": {
    "command": "jmodel",
    "alternate": "spec/javascripts/models/%s_spec.coffee",
    "template": "App.%S = DS.Model.extend"
  },  
  
  "app/assets/javascripts/controllers/*_controller.coffee": {
    "command": "jcontroller",
    "alternate": "spec/javascripts/controllers/%s_spec.coffee",

aseemk

CoffeeScript 1.7 is shaping up to be a pretty kick-ass release with significant improvements. Here are the ones I'm most excited about, in order of my own excitement.

Parentheses-free chaining

jashkenas/coffeescript#3263

Years of being wished for, finally granted!

wycats

A future version of Ember will come with a new templating engine known as HTMLBars.

The original motivation for HTMLBars was to allow helpers and properties to have better contextual information about what they were bound to.

So for example, consider a template like this:

<a href="{{url}}">{{link}}</a>

jonasschmidt

#!/usr/bin/env ruby

if `git diff --cached spec` =~ /,\s?(:focus|focus:\s?true|:focus\s?=>\s?true)/
  puts "\e[31mPlease focus and remove your :focus tags before committing :)"
  exit 1
end

sebmarkbage

setProps - depends on reading the last reconciled props from the current reconciled state of the app, at the time of the call. It also depends on an object that doesn't necessarily need to be there outside reconciliation. This is unlike setState, which is state that needs to be there. setState is queued up and merged at the time of reconciliation. Not at the time of the call. setState has a side-effect but is not a stateful nor mutative API.

isMounted - reads the current state of the tree, which may be stale if you're in a batch or reconciliation.

getDOMNode/findDOMNode - Reads the currently flushed node. This currently relies on the state of the system and that everything has flushed at this time. We could potentially do a forced render but that would still rely on the state of the system allowing us to synchronously being able to force a rerender of the system. Note: in 0.14, refs directly to DOM node will resolve to the DOM node. This allow you to get access to a node at the time of its choos

tj

var express = require('express')
  , cookieSessions = require('./cookie-sessions');

var app = express();

app.use(express.cookieParser('manny is cool'));
app.use(cookieSessions('sid'));

app.get('/', function(req, res){
  req.session.count = req.session.count || 0;

sebmarkbage

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