Nikita Vasilevsky

I'm really curious about this feature! Correct me if I'm wrong, but I assume currently we would prevent n+1 queries by explicitly preloading associations like ```ruby developers = Developer.includes(contracts: :company).order(:id).limit(2).to_a...

Hey folks, I just wanted to share an opinion that may sound a little defensive in regards to this feature. Luckily I'm not making decisions so it's just an opinion...

So indeed it seems like the `dotiw` is the cause. However I believe in this case it would be suitable to change the `dotiw` gem to support the same way...

It's not bad, I just think that it's a little unsuitable to apply it here while the issue is caused by a gem that is not a dependency of the...

It seems like for some cases we do want to be able to pass a negative index 🙈 I wonder if we could provide a more explicit public method for...

Sounds reasonable, and the change looks good. Just wanted to bump this PR 🙃

> they could be modified for a more intuitive response in this case. I'm curious in what way? Because >give the expected value (e.g. region.locations.count should return 1 and region.locations.pluck(:id)...

✅ UPD: Running into https://github.com/rubygems/rubygems/issues/5385 Most likely not related to the current thread Hey folks, sorry for chiming in 🙇 I was wondering if @ansonhoyt (or anyone experiencing the same)...

Hey folks, I'd like to see if https://github.com/rails/rails/pull/49290 achieved everything we aimed for in this PR so this one could be closed.

Hey folks, the reproduction script is passing since https://github.com/rails/rails/pull/48241 has been merged. We were not targeting this issue specifically but I'm glad the solution end up being generic enough to...