In our applications we've established this pattern of creating a concern that allows the controller to override includes. This works well in the context of controllers. If, for instance, one would fetch resources from within another concern, overriding the default includes is not an option.
Proposed solution
Chainable includes would solve this problem, because you simply could add more and more includes.
Currently this is not possible, because find resolves. Maybe a more where like approach could enable us making includes chainable.
Problem
In our applications we've established this pattern of creating a concern that allows the controller to override includes. This works well in the context of controllers. If, for instance, one would fetch resources from within another concern, overriding the default includes is not an option.
Proposed solution
Chainable includes would solve this problem, because you simply could add more and more includes. Currently this is not possible, because
findresolves. Maybe a morewherelike approach could enable us makingincludeschainable.