[Dashboard] Join operators address view and the wallet address view #3323
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
4 Skipped Deployments
|
…o kb/3254-dashboard-changes
…ew fields to the wallet details
…nts, replace scss with mui in the component
dnechay
reviewed
May 21, 2025
| <Stack width="100%"> | ||
| <TablePagination | ||
| // count is unknown but required as props | ||
| count={9999} |
There was a problem hiding this comment.
Maybe
Suggested change
| count={9999} | |
| count={Number.MAX_SAFE_INTEGER} |
then?
| Stake Info | ||
| </Typography> | ||
| <Stack gap={4}> | ||
| {amountStaked !== undefined && amountStaked !== null ? ( |
There was a problem hiding this comment.
Suggested change
| {amountStaked !== undefined && amountStaked !== null ? ( | |
| {Number.isFinite(amountStaked) && ( |
| <TableRow> | ||
| <TablePagination | ||
| // count is unknown but required as props | ||
| count={9999} |
There was a problem hiding this comment.
Maybe max sage integer here as well?
…ress in the table, add withdrawable tokens
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue tracking
Closes #3254
Figma: New design
Context behind the change
This PR implements:
Stake Infosection for wallet and operator addressesAlso in this PR I've changed components in favor of using MUI's tools instead of scss, made changes to
theme, refactored a bunch of small components (reusability, semantic html, simplified styles, hooks, imports, etc)How has this been tested?
Only locally
Release plan
Regular plan
Potential risks; What to monitor; Rollback plan
We still yet to clarify on cumulative graph and whether we want to put SearchBar in the header (most likely, these features will be integrated as a follow-up PR )