feat: add shared EstimatedChanges UI component - #369
Open
Julink-eth wants to merge 1 commit into
Open
Julink-eth wants to merge 1 commit into
Julink-eth wants to merge 1 commit into
Conversation
|
This branch was successfully deployed
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
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.



Explanation
Adds a shared EstimatedChanges Snaps JSX component to @metamask/snap-networks-utils.
The component consolidates the common transaction-confirmation UI for:
Estimated changes header and tooltip
Send and receive asset groups
Asset amount and logo display
Loading and fetching states
Scan error state
Empty estimated-changes state
Unknown asset amounts
The component accepts display-ready assets and translated labels, allowing each Snap to retain ownership of network-specific formatting and localization.
References
Checklist