Skip to content
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

feat(governance-ui#35): Add proper data for Contract params on homepage #43

Merged
merged 11 commits into from
Feb 6, 2024

Conversation

tplocic20
Copy link
Contributor

Description

Add a proper calculation of data for contract params view

Other changes

n/a

Tested

PR build and lint successful

Related issues

Backwards compatibility

n/a

Documentation

n/a

@tplocic20 tplocic20 requested review from bowd and AnnaJ-P11 January 23, 2024 10:06
Copy link

vercel bot commented Jan 23, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
governance-ui ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 6, 2024 11:16am

Copy link
Contributor

@nvtaveras nvtaveras left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a few comments but it's my first time reviewing anything related to the governance ui, so take them with a grain of salt 🙃

app/helpers/contracts.ts Outdated Show resolved Hide resolved
app/components/proposals-list/proposals-list.component.tsx Outdated Show resolved Hide resolved
app/interfaces/proposal.interface.ts Outdated Show resolved Hide resolved
app/components/proposals-list/proposals-list.component.tsx Outdated Show resolved Hide resolved
package-lock.json Outdated Show resolved Hide resolved
@tplocic20
Copy link
Contributor Author

@bowd @bayological So, during the previous grooming session we talked about the implementation of SDK.
Do you think it's a good idea to change this direct contract calls to SDK usage?

To have one and unified way

I can do this, but I need some guidance

Copy link
Member

@bayological bayological left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tplocic20 I don't think we're there yet. Were you able to get the correct total veMento displayed in the UI?

I changed the locking contract address to 0x65a1271ce7B2ec8D564A4Bc752E13A36a46e81B8 which is correct for alfajores but I am still getting 0 as the total supply in the interface. The result of the read contract call is always undefined.

This is not the same as what I see on celo scan:
image

bowd and others added 6 commits February 2, 2024 12:57
### Description

It improves the chain state helper definition and loading and exposes a `useContracts` hook used throughout the app.
The problem with this PR right now is that the addresses in the SDK are not the ones that are indexed in `The Graph` that is a separate deployment. I will migrate the indexers to this deployment as well.

After I do that, however, we will have no test proposals because the ones that I created are on the other deployment.
We need a small script to seed the deployment with some test proposals that have votes. 

### Other changes

- None

### Tested

- Verified correct contract addresses were being used with logs on chain switch :)

### Related issues

-  Fixes #49
@tplocic20 tplocic20 requested a review from bayological February 5, 2024 10:51
@tplocic20
Copy link
Contributor Author

Fixed the total supply preview

@bowd bowd merged commit 4a870d2 into develop Feb 6, 2024
3 checks passed
@bayological bayological deleted the feat/35-governance-stats-component branch April 17, 2024 16:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants