Caroline Artz carolineartz

Architecture in Elm

This document is a collection of concepts and strategies to make large Elm projects modular and extensible.

We will start by thinking about the structure of signals in our program. Broadly speaking, your application state should live in one big foldp. You will probably merge a bunch of input signals into a single stream of updates. This sounds a bit crazy at first, but it is in the same ballpark as Om or Facebook's Flux. There are a couple major benefits to having a centralized home for your application state:

There is a single source of truth. Traditional approaches force you to write a decent amount of custom and error prone code to synchronize state between many different stateful components. (The state of this widget needs to be synced with the application state, which needs to be synced with some other widget, etc.) By placing all of your state in one location, you eliminate an entire class of bugs in which two components get into inconsistent states. We also think yo

ANNOUNCEMENT

I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!

\

WARNING: Nokogiri was built against LibXML version 2.8.0, but has dynamically loaded 2.9.1

or

WARNING: Nokogiri was built against LibXML version 2.9.1, but has dynamically loaded 2.9.0

	/** @jsx React.DOM */

	var SVGComponent = React.createClass({
	render: function() {
	return this.transferPropsTo(
	<svg>{this.props.children}</svg>
	);
	}
	});

	require 'rails_helper'

	RSpec.describe TodosController, :type => :controller do

	describe "GET #index" do
	#describe "POST #create" do
	#describe "GET #show" do
	#describe "PATCH #update" do (or PUT #update)
	#describe "DELETE #destroy" do
	#describe "GET #new" do

	//
	// Module Dependencies
	// ==================================================================
	var gulp = require('gulp'),
	concat = require('gulp-concat'),
	uglify = require('gulp-uglify'),
	plumber = require('gulp-plumber'),
	sass = require('gulp-sass');

	//

	-- Extensible Records

	-- given a record
	x = { age = 42, name = "Boke" }

	-- you can clone and remove a field in the process
	{ x - age } -- { name = "Boke" }

	-- you can also add a field
	{ x \| species = "Jade Dragon" } -- { age = 42, name = "Boke", species = "Jade Dragon" }

	def lambda_test
	lam = lambda { return }
	lam.call
	puts "Hello world"
	end

	puts "Lambda Test : #{lambda_test }"

	def proc_test
	proc = Proc.new { return }

	# Original Rails controller and action
	class EmployeesController < ApplicationController
	def create
	@employee = Employee.new(employee_params)

	if @employee.save
	redirect_to @employee, notice: "Employee #{@employee.name} created"
	else
	render :new
	end

	require 'rdoc'
	converter = RDoc::Markup::ToMarkdown.new
	rdoc = File.read(ARGV[0] \|\| 'README.rdoc')
	puts converter.convert(rdoc)

	# ruby rdoc2md.rb > README.md
	# ruby rdoc2md.rb ABC.rdoc > abc.md