Feature/vaults table #345
Merged
Feature/vaults table #345
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Running Lighthouse audit... |
crypto-engineer
force-pushed
the
feature/vaults-table
branch
from
3912b7c
to
489bade
Compare
crypto-engineer
commented
Jun 20, 2022
crypto-engineer
force-pushed
the
feature/vaults-table
branch
from
04293ea
to
47695a7
Compare
tomjeatt
approved these changes
Jun 21, 2022
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.
Multi-collaterals (KSM and KINT) are supported in this table. Actually, it's an MVP version without all design details implemented. But from functionality and scalability perspectives, it's enough I think.
FYI: I minimized maintaining effort for scalability.