This repository has been archived by the owner on Sep 26, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 56
feat: Roll back the detailed balances on Explorer in favor of Wallet Profile link #494
Merged
Conversation
This file contains 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
…Wallet Profile link
Your Render PR Server URL is https://near-explorer-frontend-pr-494.onrender.com. Follow its progress at https://dashboard.render.com/web/srv-bv55bvon4r0bfdpmrh80. |
great work! @khorolets |
frol
approved these changes
Dec 4, 2020
frol
force-pushed
the
feat/wallet-profile-link
branch
from
December 4, 2020 19:05
86192f3
to
435b817
Compare
@corwinharrell @kcole16 @ilblackdragon Can you review the end result of Explorer hiding all the balances behind a link to the balances on the Wallet profile page? With lockup account: Without lockup account: |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Closes #464
We were talking through the issue with @frol and ended up removing a lot of cells in the table (FYI @icerove)