Mateus Gomes mateusg

Benchmark Bundler

Because loading gems can take longer than you think

$ curl -fsSL https://gist.github.com/jherdman/5025684/raw/a3ccd4b5308723245706b4ae315845fe951b4473/benchmark.rb | ruby
............................................................[DONE]

Gem                            Time(sec)     Pct %
--------------------------------------------------

Compose-able Query Objects in Rails

Example usage:

old_accounts = Account.where("created_at < ?", 1.month.ago)
old_abandoned_trials = AbandonedTrialQuery.new(old_accounts)

old_abandoned_trials.find_each do |account|
 account.send_offer_for_support

My issues with Modules

In researching topics for RailsCasts I often read code in Rails and other gems. This is a great exercise to do. Not only will you pick up some coding tips, but it can help you better understand what makes code readable.

A common practice to organize code in gems is to divide it into modules. When this is done extensively I find it becomes very difficult to read. Before I explain further, a quick detour on instance_eval.

You can find instance_eval used in many DSLs: from routes to state machines. Here's an example from Thinking Sphinx.

class Article &lt; ActiveRecord::Base

YARD CHEATSHEET http://yardoc.org

May 2020 - updated fork: https://gist.github.com/phansch/db18a595d2f5f1ef16646af72fe1fb0e

cribbed from http://pastebin.com/xgzeAmBn

Templates to remind you of the options and formatting for the different types of objects you might want to document using YARD.

Modules

We couldn’t find that file to show.

Friendly URLs

By default, Rails applications build URLs based on the primary key -- the id column from the database. Imagine we have a Person model and associated controller. We have a person record for Bob Martin that has id number 6. The URL for his show page would be:

/people/6

But, for aesthetic or SEO purposes, we want Bob's name in the URL. The last segment, the 6 here, is called the "slug". Let's look at a few ways to implement better slugs.

	# This Rack middleware helps solving the issue with some Rails versions which do not accept
	# a '/;q=0.6' and their variants 'Accept' request header. This header is particularly used
	# by Google Bot, and if Rails doesn't like it, it will return a 500 or 406 error to Google Bot,
	# which is not the best way to get your pages indexed.
	#
	# References:
	# - http://stackoverflow.com/questions/8881756/googlebot-receiving-missing-template-error-for-an-existing-template
	# - https://github.com/rails/rails/issues/4127
	#
	class GoogleBotAware

	MASTER=`git log --pretty=format:'%H' master \| sort`
	DEV=`git log --pretty=format:'%H' development \| sort`
	for i in `diff <(echo "${MASTER}") <(echo "${DEV}") \| grep '^>' \| sed 's/^> //'`;
	do
	git --no-pager log -1 --oneline $i;
	done

	brew update
	brew versions FORMULA
	cd `brew --prefix`
	git checkout HASH Library/Formula/FORMULA.rb # use output of "brew versions"
	brew install FORMULA
	brew switch FORMULA VERSION
	git checkout -- Library/Formula/FORMULA.rb # reset formula

	## Example: Using Subversion 1.6.17
	#

	#!/bin/bash

	# This way you can customize which branches should be skipped when
	# prepending commit message.
	if [ -z "$BRANCHES_TO_SKIP" ]; then
	BRANCHES_TO_SKIP=(master develop test)
	fi

	BRANCH_NAME=$(git symbolic-ref --short HEAD)
	BRANCH_NAME="${BRANCH_NAME##*/}"