mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
27fb356360
Instead of doing a case statement here we can have each of the objects respond to `invert`. This means that when adding new objects we don't need to increase this case statement, it's more object oriented, and let's be fair, it looks better too. Aaron and I stumbled upon this while working on some performance work in Arel. I removed `random_object` from the invert test because we don't support random objects. If you pass a random object to Arel, it should raise, not be inverted. Co-authored-by: Aaron Patterson <aaron.patterson@gmail.com> |
||
---|---|---|
.. | ||
attributes | ||
collectors | ||
nodes | ||
visitors | ||
alias_predication.rb | ||
crud.rb | ||
delete_manager.rb | ||
errors.rb | ||
expressions.rb | ||
factory_methods.rb | ||
insert_manager.rb | ||
math.rb | ||
nodes.rb | ||
order_predications.rb | ||
predications.rb | ||
select_manager.rb | ||
table.rb | ||
tree_manager.rb | ||
update_manager.rb | ||
visitors.rb | ||
window_predications.rb |