carlosramireziii

require "rspec/expectations"

RSpec::Matchers.define :allow_content_type do |*content_types|
  match do |record| 
    matcher.matches?(record, content_types)
  end

  chain :for do |attr_name|
    matcher.for(attr_name)
  end

rkhullar

import functools
import time

class timeit:
  """decorator for benchmarking"""
  def __init__(self, fmt='completed {:s} in {:.3f} seconds'):
    # there is no need to make a class for a decorator if there are no parameters
    self.fmt = fmt
  
  def __call__(self, fn):

jctosta

Screen Quick Reference

Basic

Description	Command
Start a new session with session name	screen -S <session_name>
List running sessions / screens	screen -ls
Attach to a running session	screen -x
Attach to a running session with name	screen -r

dschneider

ActionDispatch::Request.any_instance.stub(:remote_ip).and_return("192.168.0.1")

jasonrudolph

# Credit http://stackoverflow.com/a/2514279
for branch in `git branch -r | grep -v HEAD`;do echo -e `git show --format="%ci %cr" $branch | head -n 1` \\t$branch; done | sort -r

kinopyo

# in spec/support/omniauth_macros.rb
module OmniauthMacros
  def mock_auth_hash
    # The mock_auth configuration allows you to set per-provider (or default)
    # authentication hashes to return during integration testing.
    OmniAuth.config.mock_auth[:twitter] = {
      'provider' => 'twitter',
      'uid' => '123545',
      'user_info' => {
        'name' => 'mockuser',

jcasimir

Render and Redirect

The normal controller/view flow is to display a view template corresponding to the current controller action, but sometimes we want to change that. We use render in a controller when we want to respond within the current request, and redirect_to when we want to spawn a new request.

Render

The render method is very overloaded in Rails. Most developers encounter it within the view template, using render :partial => 'form' or render @post.comments, but here we'll focus on usage within the controller.

:action