Open meskill opened 1 month ago
/bounty 150
/attempt #2892
with your implementation plan/claim #2892
in the PR body to claim the bounty🙏 Thank you for contributing to tailcallhq/tailcall! 🧐 Checkout our guidelines before you get started. 💵 More about our bounty program.
Attempt | Started (GMT+0) | Solution |
---|---|---|
🟢 @meskill | #2978 |
💡 @meskill submitted a pull request that claims the bounty. You can visit your bounty board to reward.
Current implementation is checking only the fields while calculating n+1 issue. But after implementing https://github.com/tailcallhq/tailcall/issues/2639 resolvers could now be defined on types as well.
When considering entity resolver the entity resolver itself should be batched to prevent n+1 issue and that should be applied to any nested fields.
Handle resolvers on types while executing n+1 check
Example Configuration
Actual
Expected