Nicolò G. nickgnd

The introduction to Reactive Programming you've been missing

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

Commands examples

If the namespace is not used then the commands will perform on top of the default database. bundle exec rake db:create bundle exec rake db:migrate

By using the namespace we are going to use all the configuration for our alternate DB. bundle exec rake store:db:create bundle exec rake store:db:migrate

Folder Structure

Please note

While this gist has been shared and followed for years, I regret not giving more background. It was originally a gist for the engineering org I was in, not a "general suggestion" for any React app.

Typically I avoid folders altogether. Heck, I even avoid new files. If I can build an app with one 2000 line file I will. New files and folders are a pain.

"Push work down the tree"

One disadvantage of the top-down rendering approach we use is that the closer to the root of the application a component lives, the more it will be rerendered. The root component will be rerendered every time any data changes.

This is probably not a big deal for applications without much dynamic state, but let's say you have a input box at the bottom of a large tree of components (which will happen on pretty much any page containing a form). The user types, and every keystroke causes the entire app to rerender!

Well, this might be a big deal, or it might not be, depending on how you design your components. Some general guidelines will help us architect React apps that are fast by default, and don't need a whole lot of manual optimization.

	# 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

	# This script has to be run as a root user
	echo "* Updating system"
	apt-get update
	apt-get -y upgrade
	echo "* Installing packages"
	apt-get -y install build-essential libmagickcore-dev imagemagick libmagickwand-dev libxml2-dev libxslt1-dev git-core nginx redis-server curl nodejs htop

	id -u deploy &> /dev/null

	if [ $? -ne 0 ]

	# Custom rspec matcher for testing CanCan abilities.
	# Originally inspired by https://github.com/ryanb/cancan/wiki/Testing-Abilities
	#
	# Usage:
	# should have_abilities(:create, Post.new)
	# should have_abilities([:read, :update], post)
	# should have_abilities({manage: false, destroy: true}, post)
	# should have_abilities({create: false}, Post.new)
	# should not_have_abilities(:update, post)
	# should not_have_abilities([:update, :destroy], post)

	import { Component } from "React";

	export var Enhance = ComposedComponent => class extends Component {
	constructor() {
	this.state = { data: null };
	}
	componentDidMount() {
	this.setState({ data: 'Hello' });
	}
	render() {

	* {
	font-size: 12pt;
	font-family: monospace;
	font-weight: normal;
	font-style: normal;
	text-decoration: none;
	color: black;
	cursor: default;
	}

	Because I couldn't find these with a quick Google search on 28 April 2015:

	Usage:
	rails new APP_PATH [options]

	Options:
	-r, [--ruby=PATH] # Path to the Ruby binary of your choice
	# Default: /home/brian/.rvm/rubies/ruby-2.2.0/bin/ruby
	-m, [--template=TEMPLATE] # Path to some application template (can be a filesystem path or URL)
	[--skip-gemfile], [--no-skip-gemfile] # Don't create a Gemfile