feat: rpc batch requests

[ugur-eren]

Motivation and Resolution

The BatchClient class allows requests to be batched together, either by the interval amount, or at the end of the callback queue if set to 0. By batching requests, we can reduce the overhead associated with handling individual requests, optimize resource utilization and improve overall performance.

Request:

Response:

closes #758

Usage related changes

• batch option added to RpcProvider options.

Development related changes

• BatchClient class created to manage batching of requests.

Checklist:

• Performed a self-review of the code
• Rebased to the last commit of the target branch (or merged it into my branch)
• Linked the issues which this PR resolves
• Documented the changes in code (API docs will be generated automatically)
• Updated the tests
• All tests are passing

[tabaktoni]

I haven't gone into details yet, on first look, it seems good, but we need tests.
Can you please add tests for new Classes and Batch requests, we must have tests for it before merging.
Can you add a section to www/ documentation about usage? (optional - this can be done in separate PR)

[ugur-eren]

Hi @tabaktoni sorry for late reply, I didn't see the notification.
I will add the tests ASAP. There is only a single function to test, won't take long.
But about documentation, the new Batch class is only used in the RpcChannel class, it's not used externally and is not exported. If it's not preferred to have a class for this, we can also convert it to a function. But I thought a class would be easier and cleaner.
Only usage change is a new batch option. I will add this option to the documentation.

[ugur-eren]

Hi @tabaktoni sorry for late reply. I've added tests and also moved the BatchClient class to utils, instead of the src. It is ready to review.

[github-actions]

🎉 This issue has been resolved in version 6.12.0 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀