Kyle d'Oliveira

@nvasilevski You are correct that currently how to prevent an N+1 query would be to explicitly use the `includes` and that it would cause the view layer to execute db...

I can see some similarities between the two approaches. maybe @gwincr11 can correct anything that I have incorrect after trying to get up to speed with that PR. General approachs:...

I've encountered something similar with developer resistance because of the magic. However, once people been using it while it is enabled globally, they typically don't want to go back to...

So currently in this PR we have the `automatic_preloading` method that can be used both to enable or disable (very similar to how `strict_loading` works) So someone could do `Developer.order(:id).automatic_preloading(false)`...

@matthewd Any additional thoughts you have here?

@nvasilevski It's not always easy to voice (or to hear) comments in opposition to feature, but in the spirit of building the best thing, I think it is really important....

@simi Naming wise, I'm not against `smart_loading`. I do like how `automatic` does imply a little of what is does whereas `smart` may be a little unclear. That said, my...

This would be very useful to us as well. This is noted as blocked in Community, what is it blocked on?

Just pinging more here as it has been a few months with no further activity. Is there anything I can do to help move this forward more?

cc: @eileencodes I figured I'd ping you on this as you were also looking at https://github.com/rails/rails/pull/45071 which was aiming to solve a similar problem and I'd be interested in your...