diff options
| author | Xavier Noria <fxn@hashref.com> | 2012-08-06 00:27:56 +0200 |
|---|---|---|
| committer | Xavier Noria <fxn@hashref.com> | 2012-08-06 00:30:02 +0200 |
| commit | 447b6a4e678ab1618bdcd130e30c288b0a25297a (patch) | |
| tree | 6d9cb3417996517a5b237d3950c25ab32a5db098 /guides/rails_guides | |
| parent | 6126f02cf903fa206b11d2dc2eeb5f197a29b965 (diff) | |
| download | rails-447b6a4e678ab1618bdcd130e30c288b0a25297a.tar.gz rails-447b6a4e678ab1618bdcd130e30c288b0a25297a.tar.bz2 rails-447b6a4e678ab1618bdcd130e30c288b0a25297a.zip | |
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
https://github.com/rails/rails/commit/5ea6b0df9a36d033f21b52049426257a4637028d
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.
Diffstat (limited to 'guides/rails_guides')
| -rw-r--r-- | guides/rails_guides/textile_extensions.rb | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/guides/rails_guides/textile_extensions.rb b/guides/rails_guides/textile_extensions.rb index 0a002a785f..1faddd4ca0 100644 --- a/guides/rails_guides/textile_extensions.rb +++ b/guides/rails_guides/textile_extensions.rb @@ -1,5 +1,3 @@ -require 'active_support/core_ext/object/inclusion' - module RedCloth::Formatters::HTML def emdash(opts) "--" |