You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
find
resolves. Maybe a morewhere
like approach could enable us makingincludes
chainable.The text was updated successfully, but these errors were encountered: