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> |
||
|---|---|---|
| .. | ||
| delegation_test.rb | ||
| delete_all_test.rb | ||
| merging_test.rb | ||
| mutation_test.rb | ||
| or_test.rb | ||
| predicate_builder_test.rb | ||
| record_fetch_warning_test.rb | ||
| select_test.rb | ||
| update_all_test.rb | ||
| where_chain_test.rb | ||
| where_clause_test.rb | ||
| where_test.rb | ||