## Testing
1. Create a decorator for the model and its association
```ruby
class OrderHistoryDecorator < Draper::Decorator
delegate_all
end
class OrderDecorator < Draper::Decorator
delegate_all
decorates_association :order_histories, with: OrderHistoryDecorator
end
```
2. Call `respond_to?` with some ORM method allowed by the strategy
```ruby
[1] pry(main)> order.order_histories.decorate.respond_to?(:includes)
=> true
```
## References
* method_missing [usage](https://thoughtbot.com/blog/always-define-respond-to-missing-when-overriding)
## Description
Include all QueryMethods from the ORM in CollectionDecorator. The default adapter is :active_record
* Why was this change required?
It was necessary to delegate or define a method of the ORM which you are using in your decorator to make an instance of CollectionDecorator able to call it.
* Is there something you aren't happy with or that needs extra attention?
In order to support other ORM associations, we'll need to write a method `allowed?` for each strategy at `lib/draper/query_methods/load_strategy.rb`
## Testing
1. Create a decorator for the model and its association
```ruby
class OrderHistoryDecorator < Draper::Decorator
delegate_all
end
class OrderDecorator < Draper::Decorator
delegate_all
decorates_association :order_histories, with: OrderHistoryDecorator
end
```
2. Call any query method in the decorated instance
```ruby
pry(main)> Order.last.decorate.order_histories.includes(:user)
```
## References
* Issue #702
* Issue #812
oieioi