aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/test/models/warehouse_thing.rb
diff options
context:
space:
mode:
authorAkira Matsuda <ronnie@dio.jp>2016-01-28 17:13:47 +0900
committerAkira Matsuda <ronnie@dio.jp>2016-01-28 18:37:39 +0900
commitdc925119a3912ecfe0df400007163f33b99d6385 (patch)
treeb43c5b89f30504ac028b62bdde9f638b1775fbff /activerecord/test/models/warehouse_thing.rb
parenta69281614a7ed6c134d9a799419dd34dd5293a81 (diff)
downloadrails-dc925119a3912ecfe0df400007163f33b99d6385.tar.gz
rails-dc925119a3912ecfe0df400007163f33b99d6385.tar.bz2
rails-dc925119a3912ecfe0df400007163f33b99d6385.zip
Revert "Remove valid_scope_name? check - use ruby"
This reverts commit f6db31ec16e42ee7713029f7120f0b011d1ddc6c. Reason: Scope names can very easily conflict, particularly when sharing Concerns within the team, or using multiple gems that extend AR models. It is true that Ruby has the ability to detect this with the -w option, but the reality is that we are depending on too many gems that do not care about Ruby warnings, therefore it might not be a realistic solution to turn this switch on in our real-world apps.
Diffstat (limited to 'activerecord/test/models/warehouse_thing.rb')
0 files changed, 0 insertions, 0 deletions