ericelliott

// Polyfill localStorage for older browsers
(function () {
  'use strict';
  if (!window.localStorage) {
    window.localStorage = {
      getItem: function (sKey) {
        if (!sKey || !this.hasOwnProperty(sKey)) { return null; }
        return unescape(document.cookie.replace(new RegExp("(?:^|.*;\\s*)" + escape(sKey).replace(/[\-\.\+\*]/g, "\\$&") + "\\s*\\=\\s*((?:[^;](?!;))*[^;]?).*"), "$1"));
      },
      key: function (nKeyId) {

ericelliott

// Polyfill localStorage for older browsers
(function () {
  'use strict';
  if (!window.localStorage) {
    window.localStorage = {
      getItem: function (sKey) {
        if (!sKey || !this.hasOwnProperty(sKey)) { return null; }
        return unescape(document.cookie.replace(new RegExp("(?:^|.*;\\s*)" + escape(sKey).replace(/[\-\.\+\*]/g, "\\$&") + "\\s*\\=\\s*((?:[^;](?!;))*[^;]?).*"), "$1"));
      },
      key: function (nKeyId) {

ericelliott

var copy = function copy(source) {
  if (source === undefined) { return undefined; }
  return JSON.parse(JSON.stringify(source));
};

ericelliott

var env = process.env;

Object.keys(env).forEach(function(key) {
  console.log('export ' + key + '="' + env[key] +'"');
});

ericelliott

Most configuration really isn't about the app -- it's about where the app runs, what keys it needs to communicate with third party API's, the db password and username, etc... They're just deployment details -- and there are lots of tools to help manage environment variables -- not the least handy being a simple .env file with all your settings. Simply source the appropriate env before you launch the app in the given env (you could make it part of a launch script, for instance).

env files look like this:

SOMEVAR="somevalue"
ANOTHERVAR="anothervalue"

To source it:

$ source dev.env # or staging.env, or production.env, depending on where you're deploying to

ericelliott

/*

# Top down render

To prevent issues where you get errors trying to
render because your element needs to be attached to the
DOM and visible in order to manipulate without errors,
it is possible to always use a top-down rendering approach.

There are two ways to do it: The parent view can render the

ericelliott

[
  {
    "name": "uid",
    "value": "nim3x1"
  },
  {
    "name": "text",
    "value": "LOL everyone is soooooo excited #Backstage today! VIDEO:"
  },
  {

ericelliott

{ "collection" :
  {
    "href" : "/touts/pending/",

    "items": [
      {
        "href": "/touts/fk9abg",
        "body": {
          "uid": "fk9abg",
          "text": "It's safe to say that this was the best moment today. LOL #KellyandMichael",

ericelliott

Siren Samples

Siren is a hypermedia type designed for entity representation in JSON. These are some ideas on how you might represent tout collections using Siren.

window.example.pendingToutsSiren = {
  "class": [ "collection" ],
  "properties": {
    "pagination": {
      "offset": 0,

ericelliott

/*global module*/
var pkgData = require('./package.json');
module.exports = function(grunt) {
  'use strict';
  grunt.initConfig({
    pkg: '<json:package.json>',
    lint: {
      all: ['./grunt.js', './dist/*.js', './test/test.js']
    },
    jshint: {