aboutsummaryrefslogtreecommitdiffstats
path: root/RELEASING_RAILS.rdoc
diff options
context:
space:
mode:
authorRafael Mendonça França <rafaelmfranca@gmail.com>2014-06-11 17:10:26 -0300
committerRafael Mendonça França <rafaelmfranca@gmail.com>2014-06-11 17:10:42 -0300
commit15c2a5be6e326614e0952630166a35f6f7404312 (patch)
tree2417f62843fd7694260c2ac5e47be730b5189f7a /RELEASING_RAILS.rdoc
parent168dc1968c13928ce355b77ff0a0bebccfffb55b (diff)
downloadrails-15c2a5be6e326614e0952630166a35f6f7404312.tar.gz
rails-15c2a5be6e326614e0952630166a35f6f7404312.tar.bz2
rails-15c2a5be6e326614e0952630166a35f6f7404312.zip
Revert "remove unnecssary require of `to_param`, as `to_query` is already require `to_param`"
Revert "No need to require to_param, it is already required in to_query.rb" This reverts commits ccdd97662e1fb00c23c90d59f65c091904959561 and d697ee14264a90a39cdbe87857656d8b314ac9b7. Reason by @jeremy: These requires are not for implementation dependency. They ensure that requiring array conversions provides to_query, to_param, and other array conversion behaviors. The fact that to_query is implemented in terms of to_param is just a coincidence. If to_query removed its to_param require, then someone requiring array conversions would no longer have to_param available. This change removes these intentional dependencies on to_param in favor of implementation side effects—an undesirable move that's susceptible to regression.
Diffstat (limited to 'RELEASING_RAILS.rdoc')
0 files changed, 0 insertions, 0 deletions