insin

/** @jsx React.DOM */

var STATES = [
  'AL', 'AK', 'AS', 'AZ', 'AR', 'CA', 'CO', 'CT', 'DE', 'DC', 'FL', 'GA', 'HI',
  'ID', 'IL', 'IN', 'IA', 'KS', 'KY', 'LA', 'ME', 'MD', 'MA', 'MI', 'MN', 'MS',
  'MO', 'MT', 'NE', 'NV', 'NH', 'NJ', 'NM', 'NY', 'NC', 'ND', 'OH', 'OK', 'OR',
  'PA', 'RI', 'SC', 'SD', 'TN', 'TX', 'UT', 'VT', 'VA', 'WA', 'WV', 'WI', 'WY'
]

var Example = React.createClass({

rajanand02

# set prefix to control-f
set -g prefix C-f

#unbind system defined prefix
unbind C-b

# helps in faster key repetition
set -sg escape-time 0

# start session number from 1 rather than 0

mattvv

#this is a very simple, work in progress helper method for stubbing the stripe checkout.js

#this creates a fake server that will generate stripe token as if it's coming from stripe. So we can test credit card input
class FakeStripe < Sinatra::Base
  def self.boot
    instance = new
    Capybara::Server.new(instance).tap { |server| server.boot }
  end

  get '/checkout.js' do

lfender6445

Pry Cheat Sheet

• Youtube Tutorial 2013

Command Line

• pry -r ./config/app_init_file.rb - load your app into a pry session (look at the file loaded by config.ru)
• pry -r ./config/environment.rb - load your rails into a pry session

Debugger

dhh

# config/routes.rb
resources :documents do
  scope module: 'documents' do
    resources :versions do
      post :restore, on: :member
    end

    resource :lock
  end
end

traviskaufman

Better Jasmine Tests With this

On the Refinery29 Mobile Web Team, codenamed "Bicycle", all of our unit tests are written using Jasmine, an awesome BDD library written by Pivotal Labs. We recently switched how we set up data for tests from declaring and assigning to closures, to assigning properties to each test case's this object, and we've seen some awesome benefits from doing such.

The old way

Up until recently, a typical unit test for us looked something like this:

describe('views.Card', function() {

nruth

# -*- encoding : utf-8 -*-
module PayStripeHelpers
  # must be used with driver: :selenium (or :sauce?)
  def pay_stripe
    sleep(0.7) # wait for the js to create the popup in response to pressing the button
    within_frame 'stripe_checkout_app' do # must be selenium
      # fill_in 'card_number', with: '4242424242424242' no longer works
      4.times {page.driver.browser.find_element(:id, 'card_number').send_keys('4242')}

      # fill_in 'cc-exp', with: '5/2018' no longer works

somebox

Thoughts about Rails Presenters

This is a collection of links, examples and rants about Presenters/Decorators in Rails.

---

The "Decorator" pattern slowly started gaining popularity in Rails several years ago. It is not part of core Rails, and there's many different interpretations about how it should work in practice.

Jay Fields wrote about it in 2007 (before he switched back to Java and then Clojure): http://blog.jayfields.com/2007/03/rails-presenter-pattern.html

brasic

#!/usr/bin/env ruby

require 'redis'

# Clear a large number of keys matching a pattern using SCAN and
# pipelining to avoid killing the server.
class ClearKeys
  def initialize(pattern, host='localhost', postprocess_pattern=nil)
    @redis = Redis.new(host: host)
    @pattern = pattern

mlocher

#!/bin/bash
# 
# NOTICE
# A new and updated version of this script is provided at 
# https://github.com/codeship/scripts/blob/master/packages/phantomjs.sh
# Please switch to that version instead!
PHANTOMJS_VERSION="1.9.8"

# clean old version and setup directories
rm -rf ~/.phantomjs