-
Notifications
You must be signed in to change notification settings - Fork 2
Refactor/historical voting power #1568
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
base: dev
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
pikonha
left a comment
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.
some coments need to fixed and also the conflicts
| description: "Returns a list of voting power changes.", | ||
| tags: ["proposals"], | ||
| request: { | ||
| query: HistoricalVotingPowerGlobalQuerySchema, |
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.
what's the difference between this one and the historicalVotingPowerByAccountId if both receive just an address as an argument?
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.
On this one the address is not necessary. I let address as an possible argument, but it is optional. The other one (/voting-power/{address}/historical) needs the address.
The Notification System needs a route the returns votingPower historical variations for all the users of a DAO. On this pr we: