-
Notifications
You must be signed in to change notification settings - Fork 302
feat(staking): add stake accounts and supply routes #1957
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
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.
Minor nits and suggestions, nothing important. Big stuff LGTM
| } else { | ||
| const pythMint = await stakingClient.getPythTokenMint(); | ||
| return getResponse(Number(pythMint.supply)); | ||
| } |
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.
Seems a bit odd to me to have a single endpoint that has a query param that enables it to do two totally different and unrelated things. Why not just split these into separate endpoints?
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.
i 100% agree, but let's keep it the same for now since other users are already integrated using this with the old ui.
No description provided.