jtulk

// a React Component that includes the header and footer 
import React from "react";

import Header from "./../components/Header";
import Footer from "./../components/Footer";
import StaticContent from "./../components/StaticContent";

// use the route name from React Router to request the right data
const StaticContainer = ({ route }) => (
  <div>

jtulk

// stashing a webpack config for transforming ES6 Code for Node

const path = require("path");
const webpack = require("webpack");
const nodeExternals = require("webpack-node-externals");

module.exports = function(env) {
  return {
    entry: ["babel-polyfill", path.join(__dirname, "..", "server", "app.js")],
    output: {

jtulk

{
 "scripts": {
    "build:prod": "webpack --env=prod --colors --profile --json > prod.stats.json",
    "build:staging": "webpack --env=dev --colors --profile --json > staging.stats.json",
    "start": "webpack-dev-server --env=dev --open --watch --progress",
  }
}

jtulk

const initialState = {
  byId: ['1', '2', '3'],
  byHash: {
    '1': {id: '1', content: {title: 'item 1'}},
    '2': {id: '2', content: {title: 'item 2'}},
    '3': {id: '3', content: {title: 'item 3'}}
  }
}

const action1 = {

jtulk

const initialState = [
  {id: '1', content: {title: 'item 1'}},
  {id: '2', content: {title: 'item 2'}},
  {id: '3', content: {title: 'item 3'}}
]

const action = {
  type: 'update',
  id: '2',
  payload: { content: {title: 'item 2 updated' }}

jtulk

Git Strategy

We currently use Gitflow. Any features to the repository should be started as branches coming off the Development branch and be prefixed with feature/ (or an appropriate semantic prefix for commits that don't technically constitute a true 'feature', e.g. 'refactor/[refactor-description]' etc...). Any patches for production should be applied directly to Master AND Development and be prefixed with hotfix/. All branches should be associated with a pull request for merging back into Development or Master branches. For non-trivial commits (or in general), having someone else approve your pull request is preferred.

Workflow for new feature branch

• Start on Development branch (git checkout development)
• Pull recent changes (git pull)
• Create new branch (git checkout -b feature/[feature-name])
• Add changes (git status to see changes, git add . to add all changes)
• Commit changes

jtulk

// `num` now exists within the closure created by
// add, and will be available in any returned function
function add(num) {
  
  // this returned function will wait for execution with an
  // argument to be provided later
  return function partial(otherNum){
   
    // return the sum of the two arguments
    return num + otherNum

jtulk

function double(num){
  return num + num
}

function square(num){
  return num * num
}

const x = square(double(3))

jtulk

function double(num){
  return num + num
}

function square(num){
  return num * num
}

const x = double(3)
>> 6

jtulk

function partial(fn, ...args){
  return fn(...arg)
}

function basic(...args) {
  // acts on any number of passed arguments
}

partial(basic, 2, 3, 4)