Xavier Noria 447b6a4e67 removes usage of Object#in? from the code base (the method remains defined by Active Support) ... Selecting which key extensions to include in active_support/rails made apparent the systematic usage of Object#in? in the code base. After some discussion in 5ea6b0df9a we decided to remove it and use plain Ruby, which seems enough for this particular idiom. In this commit the refactor has been made case by case. Sometimes include? is the natural alternative, others a simple || is the way you actually spell the condition in your head, others a case statement seems more appropriate. I have chosen the one I liked the most in each case.		2012-08-06 00:30:02 +02:00
..
assets	Merge pull request #6383 from oscardelben/add_oscardelben_to_authors	2012-05-23 10:49:06 -07:00
code/getting_started	Remove :confirm in favor of :data => { :confirm => 'Text' } option	2012-07-18 10:32:17 -03:00
rails_guides	removes usage of Object#in? from the code base (the method remains defined by Active Support)	2012-08-06 00:30:02 +02:00
source	removes usage of Object#in? from the code base (the method remains defined by Active Support)	2012-08-06 00:30:02 +02:00
rails_guides.rb	Remove remaining require 'rubygems'	2012-05-13 13:33:20 -03:00
Rakefile	[guides] guides:generate:kindle is the new interface to generate .mobi file instead of using KINDLE=1	2012-05-28 16:20:10 -05:00
w3c_validator.rb	Remove remaining require 'rubygems'	2012-05-13 13:33:20 -03:00