-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fetch and Display Builder Count from BatchRegistry Contract #17
Fetch and Display Builder Count from BatchRegistry Contract #17
Conversation
@Superior212 is attempting to deploy a commit to the BuidlGuidl Team on Vercel. A member of the Team first needs to authorize it. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@phipsae i have refactor the page kindly review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the adjustments!
Just a little thing to change, see below.
@phipsae I have adjusted the suggestions. I hope we are good to go. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a little thing to change and then we are good to go.
@phipsae have remove the |
Thank you! So let's merge! |
Description
This pull request addresses the display of the number of builders who have checked into the contract within the
packages/nextjs/app/page.tsx
file. Currently, a placeholder string "To Be implemented" is displayed, which does not provide any useful information to users.Proposed Changes
Replace the placeholder string with the actual count of builders who have checked in, which will be retrieved from the
BatchRegistry
contract.Implement a method to fetch this count and ensure it updates dynamically when the data changes.
I have read the contributing docs (if this is your first contribution)
This is not a duplicate of any existing pull request
_Closes #5
Address:0x62CeF3Ca8b52a9C69a17236CA2c56Cdb7a383E8e