"Prime" items about batch-loader

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[exAspArk]

Hi @maletor,

Thank you for sharing the idea! I imagine the following scenario where it can be useful:

class Post
  belongs_to :user
end

class User
  belongs_to :avatar
end

class Avatar
end

def lazy_avatar(user)
  BatchLoader.for(user.id).batch do |user_ids, loader|
    Avatar.where(user_id: user_ids).each do |avatar|
      loader.call(avatar.user_id, avatar)
    end
  end
end

def lazy_user(post)
  BatchLoader.for(post.user_id).batch do |user_ids, loader|
    User.where(id: user_ids).each do |user|
    # ^ we could use User.where(...).includes(:avatar) to prime in this batch
      loader.call(user.id, user)
    end
  end
end

Implementing the "prime" is possible. But the main challenge is to design a good API for developers. BatchLoader doesn't require developers to define and share the "loaders" (dataloader) or separate classes, everything lives in the block. It simplifies the usage but doesn't allow to share one BatchLoader reference in another.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.