sebmarkbage

The Rules of React

All libraries have subtle rules that you have to follow for them to work well. Often these are implied and undocumented rules that you have to learn as you go. This is an attempt to document the rules of React renders. Ideally a type system could enforce it.

What Functions Are "Pure"?

A number of methods in React are assumed to be "pure".

On classes that's the constructor, getDerivedStateFromProps, shouldComponentUpdate and render.

cybrox

/**
 * This is a very simple example of an ember component to integrate
 * nnick/chart.js in an ember.js application. Basically, it is simply
 * using the components hook to create a ChartJS canvas element.
 * Additionally, it supports an update property that allows you to
 * let the chart re-rendet if your data or options change. Chart.js
 * doesn't support updating its data so this will just create a new
 * chart on the given canvas.
 * 
 * Example usage in a handlebars template:

FGRibreau

//
// Usage: require('./pid')("myapp");
//
var fs        = require('fs');

module.exports = function(appname){
  process.title = appname;

  var PID_FILE  = "/usr/local/var/run/"+process.title+".pid";

pixelhandler

var application_root = __dirname,
    express = require("express"),
    path = require("path"),
    mongoose = require('mongoose');

var app = express.createServer();

// database

mongoose.connect('mongodb://localhost/ecomm_database');